(shimmering corporate music) >> Hey, everyone. Welcome back to our conversation with Hitachi Vantara. Lisa Martin here with Russell Skingsley, the CTO and Global VP of Technical Sales at Hitachi Vantara. Russell, welcome to the program. >> Hiya, Lisa! Nice to be here! >> Yeah, great to have you. So, here we are, at the end of calendar year 2022. What are some of the things that you're hearing out in the field in terms of customers' priorities for 2023? >> Yeah, good one. Just to set the scene here, we tend to deal with enterprises that have mission-critical IT environments and this has been been in our heritage and continues to be our major strength. So, just to set the scene here, that's the type of customers predominantly I'd be hearing from and so, that's what you're going to hear about here. Now, in terms of 2023, one of the macro concerns that's hitting almost all of our customers right now, as you can probably appreciate, is power consumption and closely related to that is the whole area of ESG and de-carbonization and all of that sort of thing, and I'm not going to spend a lot of time on that one because that would be a whole session in itself really, but sufficient to say, it is a priority for us and we are very active in that area. So, aside from that one, that big one, there's also a couple that are pretty much in common for most of our customers and we're in areas that we can help. One of those is in an exponential growth of the amount of data. It's predicted that the world's data is going to triple by 2025 as opposed to where it was in 2020 and I think everyone's contributing to that, including a lot of our customers. So, just the act of managing that amount of data is a challenge in itself and I think closely related to that, a desire to use that data better to be able to gain more business insights and potentially create new business outcomes and business ideas is another one of those big challenges. In that sense, I think a lot of our customers are in what I would kind of call, I affectionately call, the Post-Facebook Awakening Era, and what I mean by that is our traditional businesses, you know, when Facebook came along, they kind of illustrated, hey, I can actually make some use out of what is seemingly an enormous amount of useless data, which is exactly what Facebook did. They took a whole lot of people's, yeah, the minutiae of people's lives, and turned it into, you know, advertising revenue by gaining insights from those, you know, sort of seemingly useless bits of data. >> Right. >> Yeah, right, and I think this actually gave rise to a lot of digital business at that time. You know, this whole idea of all you really need to be successful and disrupt the business is a great idea, you know, an app and a whole bunch of data to power it and I think that a lot of our traditional customers are looking at this and wondering how do they get into the act because they've been collecting data for decades, an enormous amount of data. Right. >> Yeah, every company these days has to be a data company, but to your point, it's got to be able to extract those insights, monetize it, and create real value, new opportunities for the business, at record speed. >> Yes, that's exactly right, and so, being able to wield that data somehow, it kind of turns out our customer's attentions to the type of infrastructure they've got as well. I mean, if you think about those companies that have been really successful in leveraging that data or a lot of them have, especially in the early days, leverage the Cloud to be able to build out their capabilities and the reason why the Cloud became such a pivotal part of that is because it offered self-service IT and, you know, easy development platforms to those people that had these great ideas. All they needed was access to, you know, the provider's website and a credit card and now, all of a sudden, they could start to build a business from that and I think a lot of our traditional IT customers are looking at this and thinking, now, how do I build a similar sort of infrastructure? How do I provide that kind of self-service capability to the owners of business inside my company rather than the IT company sort of being a gatekeeper to a selected set of software packages? How now do I provide this development platform for those internal users? And I think this is why, really, Hybrid Cloud has become the defacto IT sort of architectural standard even for quite traditional, you know, IT companies. >> So, when it comes to Hybrid Cloud, what are some of the challenges the customers are facing? And then, I know Hitachi has a great partner ecosystem. How are partners helping Hitachi Vantara and its customers to eliminate or solve some of those Hybrid Cloud challenges? >> Yeah, it's a great question and, you know, it's not 1975 anymore. It's not like you're going to get all of your IT needs from one vendor. Hybrid by, sort of, its, you know, by definition, is going to involve multiple pieces and so, there basically is no hybrid at all without a partner ecosystem. You really can't get everything at a one-stop shop like you used to, but even if you think about the biggest public Cloud provider on the planet, AWS, even it has a marketplace for partner solutions. So, even they see, even for customers that might consider themselves to be all in on Public Cloud, they are still going to need other pieces, which is where their marketplace comes in. Now, for us, you know, we're a company that, we've been in the IT business for over 60 years, one of the few that could claim that sort of heritage, and, you know, we've seen a lot of this type of change ourselves, this change of attitude from being able to provide everything yourself to being someone who contributes to an overall ecosystem. So, partners are absolutely essential, and so now, we kind of have a partner-first philosophy when it comes to our routes to market on, you know, not just our own products in terms of, you know, a resale channel or whatever, but also making sure that we are working with some of the biggest players in Hybrid infrastructure and determining where we can add value to that in our own solutions and so, you know, when it comes to those partner ecosystems, we're always looking for the spaces where we can best add our own capability to those prevailing IT architectures that are successful in the marketplace and, you know, I think that it's probably fair to say, you know, for us, first and foremost, we have a reputation for having the biggest, most reliable storage infrastructure available on the planet and we make no apologies for the fact that we tout our speeds and feeds and uptime supremacy. You know, a lot of our competitors would suggest that, hey, speeds and feeds don't matter, but, you know, that's kind of what you say when you're not the fastest or not the most reliable. You know, of course they matter and for us, the way that we look at this is we say, let's look at who's providing the best possible Hybrid solutions and let's partner with them to make those solutions even better. That's the way we look at it. >> Can you peel the onion a little bit on the technology underpinning the solutions? Give me a glimpse into that and then maybe add some color in terms of how partners are enhancing that. >> Yeah, let me do that with a few examples here and maybe what I can do is I can sort of share some insight about the way we think with partnering with particular people and why it's a good blend or why we see that technologically it's a good blend. So, for example, the work we do with VMware, which we consider to be one of our most important Hybrid Cloud partners and in fact, it's my belief they have one of the strongest Hybrid Cloud stories in the industry. It resonates really strongly with our customers as well, but, you know, we think it's made so much better with the robust underpinnings that we provide. We're one of the few storage vendors that provides a 100% data availability guarantee. So, we take that sort of level of reliability and we add other aspects like life cycle management of the underpinning infrastructure. We combine that with what VMware's doing and then, when you look at our converged, or hyper-converged, solutions with them, it's a 'better together' story where you now have what is one of the best Hybrid Cloud stories in the industry with VMware, but now, for the on-premise part especially, you've now added 100% data availability guarantee, and you've made managing the underlying infrastructure so much easier through the tools that we provide that go down to that level, a level underneath, where VMware are, and so, that's VMware, and I've got a couple more examples just to sort of fill that out a bit. >> Sure. >> Cisco is another part, a very strong partner of ours, a key partner, and, I mean, you look at Cisco, they're a $50,000,000,000 IT provider, and they don't have a dedicated storage infrastructure of their own, so they're going to partner with someone. From our perspective, we look at Cisco's customers and we look at them and think, they're very similar to our own in terms of they're known to appreciate performance and reliability and a bit of premium in quality and we think we match with them quite well. They're already buying what we believe are the best converged platforms in the industry from Cisco, so it makes sense that those customers would want to compliment that investment with the best arrays, best storage arrays, they can get, and so, we think we are helping Cisco's customers make the most of their decision to be UCS customers. Final one for you, Lisa, by way of example. We have a relationship with Equinix and, you know, Equinix is the world's sort of leading Colo provider and the way I think they like to think of themselves, and I too tend to agree with them, is they're one of the most compelling high-speed interconnect networks in the world. They're connected to all of the significant Cloud providers in most of the locations around the world. We have a relationship with them where we find we have customers in common who really love the idea of compute from the Cloud. Compute from the Cloud is great because compute is something that you are doing for a set period of time and then it's over. You, like, you have a task, you do some compute, it's done. Cloud is beautiful for that. Storage on the other hand is very long-lived. Storage doesn't tend to operate in that same sort of way. It sort of just becomes a bigger and bigger blob over time and so, the cost model around Public Cloud and storage is not as compelling as it is for compute, and so, with our relationship with Equinix, we help our customers to be able to create, let's call it a data anchor point, where they put our arrays into an Equinix location and then they utilize Equinix as high-speeding, interconnects to the Cloud providers to take the compute from them. So, they take the compute from the Cloud providers and they own their own storage, and in this way, they feel like, we've now got the best of all worlds. >> Right. >> What I hope that illustrates Lisa is, with those three examples, is we are always looking for ways to find our key advantages with any given, you know, alliance partner's advantages. >> Right. What are, when you're in customer conversations, in our final few minutes here I want to get, what are some of the key differentiators that you talk about when you're in customer conversations and then how does the partner ecosystem fit into Hitachi Vantara as a service business? We'll start with differentiators and then let's move into the as-a-service business so we can round out with that. >> Okay, let's just start with the differentiators. You know, firstly, and hopefully, I've kind of, I've hit this point hard enough. We do believe that we have the fastest and most reliable storage infrastructure on the planet. This is kind of what we are known for and customers that are working with us already sort of have an appreciation for that and so, they're looking for, okay, you've got that. Now, how can you make my Hybrid Cloud aspirations better? So, we do have that as a fundamental, right? So, but secondly, I'd say, I think it's also because we go beyond just storage management and into the areas of data management. >> Okay. >> You know, we've got solutions that are not just about storing the bits. We do think that we do that very well, but we also have solutions that move into the areas of enrichment of the data, cataloging of the data, classification of the data, and most importantly, analytics. So, you know, we think it's, some of our competitors just stop at storing stuff and some of our competitors are in the analytics space, but we feel that we can bridge that and we think that that's a competitive advantage for us. >> Right. >> One of the other areas that I think is key for us as well is, as I said, we're one of the few vendors who've been in the marketplace for 60 years and we think this gives us a more nuanced perspective about things. There are many things in the industry, trends that have happened over time, where we feel we've seen this kind of thing before and I think we will see it again, but you only really get that perspective if you are long-lived in the industry and so, we believe that our conversations with our customers bear a little bit more sophistication. It's not just about what's the latest and greatest trends. >> Right. We've got about one minute left. Can you round us out with how the partner ecosystem is playing a role in the as-a-service business? >> They're absolutely pivotal in that, you know? We ourselves don't own data centers, right? So, we don't provide our own Cloud services out. So, we are 100% partner-focused when it comes to that aspect. Our formula is to help partners build their Cloud services with our solutions and then on-sell them to their customers as a service. You know, and by quick way of example, VMware, for example, they've got nearly 5,000 partners selling VMware Cloud services. 5,000 blows me away and many of them are our partners too. So, we kind of see this as a virtuous cycle. We've got product, we've got an an alliance with VMware, and we work together with partners in common for the delivery of an as-a-service business. >> Got it. So, as you said, the partner ecosystem, it's absolutely pivotal. Russell, it's been a pleasure having you on the program talking about all things Hybrid Cloud challenges and how Hitachi Vantara is working with its partner ecosystems to really help customers across industries solve those big problems. We really appreciate your insights and your time. >> Thank you very much, Lisa! >> Thanks, Russell. You're watching theCUBE, the leader in live tech coverage!

>>Okay. We're back with Ari Basu, who is Cisco's resident philosopher, who also holds a master's in computer science. We're gonna have to unpack that a little bit and Najati chair he who's technical lead at Cisco. Welcome guys. Thanks for coming on the cube. >>Happy to be here. Thanks a >>Lot. All right, let's get into it. We want you to explain how Cisco validated the SBRI technology and the proof points that, that you have, that it actually works as advertised. So first Outre tell first, tell us about Cisco tech. What does Cisco tech do? >>So T is otherwise it's an acronym for technical assistance center is Cisco's support arm, the support organization, and, you know, the risk of sounding like I'm spotting a corporate line. The, the easiest way to summarize what tag does is provide world class support to Cisco customers. What that means is we have about 8,000 engineers worldwide, and any of our Cisco customers can either go on our web portal or call us to open a support request. And we get about 2.2 million of these support requests a year. And what these support requests are, are essentially the customer will describe something that they need done some networking goal that they have, that they wanna accomplish. And then it's tax job to make sure that that goal does get accomplished. Now, it could be something like they're having trouble with an existing network solution, and it's not working as expected, or it could be that they're integrating with a new solution. >>They're, you know, upgrading devices, maybe there's a hardware failure, anything really to do with networking support and, you know, the customer's network goals. If they open up a case for request for help, then tax job is to, is to respond and make sure the customer's, you know, questions and requirements are met about 44% of these support requests are usually trivial and, you know, can be solved within a call or within a day. But the rest of tax cases really involve getting into the network device, looking at logs. It's a very technical role. It's a very technical job. You're look you're, you need to be conversing with network solutions, their designs protocols, et cetera. >>Wow. So 56% non-trivial. And so I would imagine you spend a lot of time digging through through logs. Is that, is that true? Can you quantify that like, you know, every month, how much time you spend digging through logs and is that a pain point? >>Yeah, it's interesting. You asked that because when we started this on this journey to augment our support engineers workflow with zebra solution, one of the things that we did was we went out and asked our engineers what their experience was like doing log analysis. And the anecdotal evidence was that on average, an engineer will spend three out of their eight hours reviewing logs, either online or offline. So what that means is either with the customer live on a WebEx, they're going to be going over logs, network, state information, et cetera, or they're gonna do it offline, where the customer sends them the logs, it's attached to a, you know, a service request and they review it and try to figure out what's going on and provide the customer with information. So it's a very large chunk of our day. You know, I said 8,000 plus engineers, and so three hours a day, that's 24,000 man hours a day spent on long analysis. >>Now the struggle with logs or analyzing logs is there by out of necessity. Logs are very contr contr. They try to pack a lot of information in a very little space. And this is for performance reasons, storage reasons, et cetera, BEC, but the side effect of that is they're very esoteric. So they're hard to read if you're not conversant, if you're not the developer who wrote these logs or you or you, aren't doing code deep dives. And you're looking at where this logs getting printed and things like that, it may not be immediately obvious or even after a low while it may not be obvious what that log line means or how it correlates to whatever problem you're troubleshooting. So it requires tenure. It requires, you know, like I was saying before, it requires a lot of knowledge about the protocol what's expected because when you're doing log analysis, what you're really looking for is a needle in a haystack. You're looking for that one anomalous event, that single thing that tells you this shouldn't have happened. And this was a problem right now doing that kind of anomaly detection requires you to know what is normal. It requires, you know, what the baseline is. And that requires a very in-depth understanding of, you know, the state changes for that network solution or product. So it requires time, tenure and expertise to do well. And it takes a lot of time even when you have that kind of expertise. >>Wow. So thank you, archery. And Najati, that's, that's about, that's almost two days a week for, for a technical resource. That's that's not inexpensive. So what was Cisco looking for to sort of help with this and, and how'd you stumble upon zebra? >>Yeah, so, I mean, we have our internal automation system, which has been running more than a decade now. And what happens is when a customer attaches a log bundle or diagnostic bundle into the service request, we take that from the Sr we analyze it and we represent some kind of information. You know, it can be alert or some tables, some graph to the engineer, so they can, you know, troubleshoot this particular issue. This is an incredible system, but it comes with its own challenges around maintenance to keep it up to date and relevant with Cisco's new products or new version of the product, new defects, new issues, and all kind of things. And when I, what I mean with those challenges are, let's say Cisco comes up with a product today. We need to come together with those engineers. We need to figure out how this bundle works, how it's structured out. >>We need to select individual logs, which are relevant and then start modeling these logs and get some values out of those logs, using pars or some rag access to come to a level that we can consume the logs. And then people start writing rules on top of that abstraction. So people can say in this log, I'm seeing this value together with this other value in another log, maybe I'm hitting this particular defect. So that's how it works. And if you look at it, the abstraction, it can fail the next time. And the next release when the development or the engineer decides to change that log line, which you write that rag X, or we can come up with a new version, which we completely change the services or processes, then whatever you have wrote needs to be re written for that new service. And we see that a lot with products, like for instance, WebEx, where you have a very short release cycle that things can change maybe the next week with a new release. >>So whatever you are writing, especially for that abstraction and for those rules are maybe not relevant with that new release. With that being sake, we have a incredible rule creation process and governance process around it, which starts with maybe a defect. And then it takes it to a level where we have an automation in place. But if you look at it, this really ties to human bandwidth. And our engineers are really busy working on, you know, customer facing, working on issues daily and sometimes creating these rules or these pars are not their biggest priorities, so they can be delayed a bit. So we have this delay between a new issue being identified to a level where we have the automation to detect it next time that some customer faces it. So with all these questions and with all challenges in mind, we start looking into ways of actually how we can automate these automations. >>So these things that we are doing manually, how we can move it a bit further and automate. And we had actually a couple of things in mind that we were looking for and this being one of them being, this has to be product agnostic. Like if Cisco comes up with a product tomorrow, I should be able to take it logs without writing, you know, complex regs, pars, whatever, and deploy it into this system. So it can embrace our logs and make sense of it. And we wanted this platform to be unsupervised. So none of the engineers need to create rules, you know, label logs. This is bad. This is good. Or train the system like which requires a lot of computational power. And the other most important thing for us was we wanted this to be not noisy at all, because what happens with noises when your level of false PE positives really high your engineers start ignoring the good things between that noise. >>So they start the next time, you know, thinking that this thing will not be relevant. So we want something with a lot or less noise. And ultimately we wanted this new platform or new framework to be easily adaptable to our existing workflows. So this is where we started. We start looking into the, you know, first of all, internally, if we can build this thing and also start researching it, and we came up to Zeum actually Larry, one of the co co-founders of Zeum. We came upon his presentation where he clearly explained why this is different, how this works, and it immediately clicked in. And we said, okay, this is exactly what we were looking for. We dived deeper. We checked the block posts where SBRI guys really explained everything very clearly there, they are really open about it. And most importantly, there is a button in their system. >>So what happens usually with AI ML vendors is they have this button where you fill in your details and sales guys call you back. And, you know, we explain the system here. They were like, this is our trial system. We believe in the system, you can just sign up and try it yourself. And that's what we did. We took our, one of our Cisco live DNA center, wireless platforms. We start streaming logs out of it. And then we synthetically, you know, introduce errors, like we broke things. And then we realized that zebra was really catching the errors perfectly. And on top of that, it was really quiet unless you are really breaking something. And the other thing we realized was during that first trial is zebra was actually bringing a lot of context on top of the logs. During those failures, we work with couple of technical leaders and they said, okay, if this failure happens, I I'm expecting this individual log to be there. And we found out with zebra, apart from that individual log, there were a lot of other things which gives a bit more context around the root columns, which was great. And that's where we wanted to take it to the next level. Yeah. >>Okay. So, you know, a couple things to unpack there. I mean, you have the dart board behind you, which is kind of interesting, cuz a lot of times it's like throwing darts at the board to try to figure this stuff out. But to your other point, Cisco actually has some pretty rich tools with AppD and doing observability and you've made acquisitions like thousand eyes. And like you said, I'm, I'm presuming you gotta eat your own dog food or drink your own champagne. And so you've gotta be tools agnostic. And when I first heard about Z zebra, I was like, wait a minute. Really? I was kind of skeptical. I've heard this before. You're telling me all I need is plain text and, and a timestamp. And you got my problem solved. So, and I, I understand that you guys said, okay, let's run a POC. Let's see if we can cut that from, let's say two days a week down to one day, a week. In other words, 50%, let's see if we can automate 50% of the root cause analysis. And, and so you funded a POC. How, how did you test it? You, you put, you know, synthetic, you know, errors and problems in there, but how did you test that? It actually works Najati >>Yeah. So we, we wanted to take it to the next level, which is meaning that we wanted to back test is with existing SARS. And we decided, you know, we, we chose four different products from four different verticals, data center, security, collaboration, and enterprise networking. And we find out SARS where the engineer put some kind of log in the resolution summary. So they closed the case. And in the summary of the Sr, they put, I identified these log lines and they led me to the roots and we, we ingested those log bundles. And we, we tried to see if Zeum can surface that exact same log line in their analysis. So we initially did it with archery ourself and after 50 tests or so we were really happy with the results. I mean, almost most of them, we saw the log line that we were looking for, but that was not enough. >>And we brought it of course, to our management and they said, okay, let's, let's try this with real users because the log being there is one thing, but the engineer reaching to that log is another take. So we wanted to make sure that when we put it in front of our users, our engineers, they can actually come to that log themselves because, you know, we, we know this platform so we can, you know, make searches and find whatever we are looking for, but we wanted to do that. So we extended our pilots to some selected engineers and they tested with their own SRSS. Also do some back testing for some SARS, which are closed in the past or recently. And with, with a sample set of, I guess, close to 200 SARS, we find out like majority of the time, almost 95% of the time the engineer could find the log they were looking for in zebra analysis. >>Yeah. Okay. So you were looking for 50%, you got to 95%. And my understanding is you actually did it with four pretty well known Cisco products, WebEx client DNA center, identity services, engine ISE, and then, then UCS. Yes. Unified pursuit. So you use actual real data and, and that was kind of your proof proof point, but Ari. So that's sounds pretty impressive. And, and you've have you put this into production now and what have you found? >>Well, yes, we're, we've launched this with the four products that you mentioned. We're providing our tech engineers with the ability, whenever a, whenever a support bundle for that product gets attached to the support request. We are processing it, using sense and then providing that sense analysis to the tech engineer for their review. >>So are you seeing the results in production? I mean, are you actually able to, to, to reclaim that time that people are spending? I mean, it was literally almost two days a week down to, you know, a part of a day, is that what you're seeing in production and what are you able to do with that extra time and people getting their weekends back? Are you putting 'em on more strategic tasks? How are you handling that? >>Yeah. So, so what we're seeing is, and I can tell you from my own personal experience using this tool, that troubleshooting any one of the cases, I don't take more than 15 to 20 minutes to go through the zebra report. And I know within that time either what the root causes or I know that zebra doesn't have the information that I need to solve this particular case. So we've definitely seen, well, it's been very hard to measure exactly how much time we've saved per engineer, right? What we, again, anecdotally, what we've heard from our users is that out of those three hours that they were spending per day, we're definitely able to reclaim at least one of those hours and, and what, even more importantly, you know, what the kind of feedback that we've gotten in terms of, I think one statement that really summarizes how Zebra's impacted our workflow was from one of our users. >>And they said, well, you know, until you provide us with this tool, log analysis was a very black and white affair, but now it's become really colorful. And I mean, if you think about it, log analysis is indeed black and white. You're looking at it on a terminal screen where the background is black and the text is white, or you're looking at it as a text where the background is white and the text is black, but what's what they're really trying to say. Is there hardly any visual cues that help you navigate these logs, which are so esoteric, so dense, et cetera. But what XRM does is it provides a lot of color and context to the whole process. So now you're able to quickly get to, you know, using their word cloud, using their interactive histogram, using the summaries of every incident. You're very quickly able to summarize what might be happening and what you need to look into. >>Like, what are the important aspects of this particular log bundle that might be relevant to you? So we've definitely seen that a really great use case that kind of encapsulates all of this was very early on in our experiment. There was, there was this support request that had been escalated to the business unit or the development team. And the tech engineer had really, they, they had an intuition about what was going wrong because of their experience because of, you know, the symptoms that they'd seen. They kind of had an idea, but they weren't able to convince the development team because they weren't able to find any evidence to back up what they thought was happening. And we, it was entirely happenstance that I happened to pick up that case and did an analysis using Seebri. And then I sat down with the attack engineer and we were very quickly within 15 minutes, we were able to get down to the exact sequence of events that highlighted what the customer thought was happening, evidence of what the, so not the customer, what the attack engineer thought was the, was a root cause. It was a rude pause. And then we were able to share that evidence with our business unit and, you know, redirect their resources so that we could change down what the problem was. And that really has been, that that really shows you how that color and context helps in log analysis. >>Interesting. You know, we do a fair amount of work in the cube in the RPA space, the robotic process automation and the narrative in the press when our RPA first started taking off was, oh, it's, you know, machines replacing humans, or we're gonna lose jobs. And, and what actually happened was people were just eliminating mundane tasks and, and the, the employee's actually very happy about it. But my question to you is, was there ever a reticence amongst your team? Like, oh, wow, I'm gonna, I'm gonna lose my job if the machine's gonna replace me, or have you found that people were excited about this and what what's been the reaction amongst the team? >>Well, I think, you know, every automation and AI project has that immediate gut reaction of you're automating away our jobs and so forth. And there is initially there's a little bit of reticence, but I mean, it's like you said, once you start using the tool, you realize that it's not your job, that's getting automated away. It's just that your job's becoming a little easier to do, and it's faster and more efficient. And you're able to get more done in less time. That's really what we're trying to accomplish here at the end of the day, rim will identify these incidents. They'll do the correlation, et cetera. But if you don't understand what you're reading, then that information's useless to you. So you need the human, you need the network expert to actually look at these incidents, but what we are able to skin away or get rid of is all of the fat that's involved in our, you know, in our process, like without having to download the bundle, which, you know, when it's many gigabytes in size, and now we're working from home with the pandemic and everything, you're, you know, pulling massive amounts of logs from the corporate network onto your local device that takes time and then opening it up, loading it in a text editor that takes time. >>All of these things are we're trying to get rid of. And instead we're trying to make it easier and quicker for you to find what you're looking for. So it's like you said, you take away the mundane, you take away the, the difficulties and the slog, but you don't really take away the work, the work still needs to be done. >>Yeah. Great guys. Thanks so much. Appreciate you sharing your story. It's quite, quite fascinating. Really. Thank you for coming on. >>Thanks for having us. >>You're very welcome. Okay. In a moment, I'll be back to wrap up with some final thoughts. This is Dave Valante and you're watching the, >>So today we talked about the need, not only to gain end to end visibility, but why there's a need to automate the identification of root cause problems and doing so with modern technology and machine intelligence can dramatically speed up the process and identify the vast majority of issues right out of the box. If you will. And this technology, it can work with log bundles in batches, or with real time data, as long as there's plain text and a timestamp, it seems Zebra's technology will get you the outcome of automating root cause analysis with very high degrees of accuracy. Zebra is available on Preem or in the cloud. Now this is important for some companies on Preem because there's really some sensitive data inside logs that for compliance and governance reasons, companies have to keep inside their four walls. Now SBRI has a free trial. Of course they better, right? So check it out@zebra.com. You can book a live demo and sign up for a free trial. Thanks for watching this special presentation on the cube, the leader in enterprise and emerging tech coverage on Dave Valante and.

(upbeat music) >> Full stack observability is all the rage today. As businesses lean into digital, customer experience becomes ever more important. Why? Well, it's obvious, fickle consumers can switch brands in the blink of an eye or the click of a mouse. Technology companies have sprung into action and the observability space is getting pretty crowded in an effort to simplify the process of figuring out the root cause of application performance problems without an army of PhDs and lab coats, also known as endlessly digging through logs, for example. We see decades old software companies that have traditionally done monitoring or log analytics and or application performance management stepping up their game. These established players, you know, they typically have deep feature sets and sometimes purpose-built tools that attack one particular segment of the marketplace. And now they're pivoting through M&A and some organic development trying to fill gaps in their portfolio. And then, you got all these new entrants coming to the market, claiming end to end visibility across the so-called modern cloud and now edge native stacks. Meanwhile, cloud players are gaining traction and participating through a combination of native tooling combined with strong ecosystems to address this problem. But, you know, recent survey research from ETR confirms our thesis that no one company has it all. Here's the thing. Customers just want to figure out the root cause as quickly and as efficiently as possible. It's one thing to observe the stack end to end, but the question is who is automating the observers? And that's why we're here today. Hello, my name is Dave Vellante and welcome to this special Cube presentation where we dig into root cause analysis, and specifically, how one company, Zebrium, is using unsupervised machine learning to detect anomalies and pinpoint root causes and delivering it as an automated service. And in this session, we have two deep dives. First, we're going to dig into this exciting new field of RCaaS, Root Cause As A Service with two of the founders and technical experts behind Zebrium. And then we bring in two technical experts from Cisco, an early Zebrium customer who ran a POC with Zebrium's service, automating and identifying root cause problems within four very well established and well known Cisco product lines, including WebEx Client and UCS. I was pretty amazed at the results and I think you'll be impressed as well. So thanks for being here. Let's get started. With me right now is Larry Lancaster, who's a founder and CTO of Zebrium. And he's joined by Rod Bagg, who's the founder and vice president of engineering at the company. Gents, welcome. Thanks for coming on. >> Thanks. >> Okay. >> It's good to be here. >> It's good to be here >> All right Rod, talk to me. Talk to me about software downtime, what root cause means, all the buzzwords in your domain, MTTR and SLO. What do we need to know? >> Yeah, I mean, it's like you said. I mean, it's extremely important to our customers and to most businesses out there to drive uptime and avoid as much downtime as possible. So, you know, when you think about it, all of these businesses, most companies nowadays, either their product is software and it's running, you know, running on the web and that's how you get a point click. Or the business depends on, you know, internal systems to drive their business and to run it. When that is down, that is hugely impacting to them. So if you take a look, you know, way back, you know, 20, 30 years ago, software was simple. You know, there wasn't much to it. It was pretty monolithic and maybe it took a couple of people to maintain it and keep it running. There wasn't really anything complicated about it. It was a single tenant piece of software. Today's software is so complicated, often running, you know, maybe hundreds of services to keep that or to actually implement what that software is doing. So as you point out, you know, enter the sort of observability space and the tools that are now in use to help monitor that software and make sure when something goes wrong, they know about it But there's kind of an interesting stat around the observability space. So when you look at observability in the context or through the lens of the cost of downtime, it's really interesting. So observability tools are about a $20 billion market, okay? But the cost of downtime, even with that in place, is still hundreds of billions of dollars. So you're not taking much of a bite out of what the real problem is. You have to solve root cause and get to that fast. So it's all great to know that something went wrong but you got to know why. And it's our contention here that, you know, really, when you take a look at the observability space, you have metrics, that's a great tool. I mean, there's lots of great tools out there, you know, around metrics monitoring that's going to tell you when something went wrong. It's very rarely it's going to tell you why. Similarly for tracing, it's going to point you to where the issue is. It's going to take you through that stack and probably pinpoint where you're being, you know where it's happening or where something is running slow, potentially. So that's great. But again, the root cause of why it's happening is going to be buried in log files. And I can expand on that a little bit more but you know, when you're a software developer and you're writing your software, those log files are a wealth of information. It's just a set of breadcrumbs that are littered with facts about how the software is behaving and why it's doing what it's doing, or why it went wrong. And it's that that really gets you to the root cause very fast. And that's our contention, is that these software systems are so complex nowadays and that the root cause is lying in those logs. So how do you get there fast? You know, we would contend that you better automate that or you are just doomed for failure. And that's where we come in. >> Great. >> Getting to that root cause. >> Thank you, Rod. You know, it's interesting you talk about the $20 billion market. There's an analogy with security, right? We spend 80, $100 billion a year on securing our infrastructure, and yet we lose probably closer to a trillion dollars a year in breaches. And there's a similar analogy here. 20 billion could be 5X in downtime impacts or more. Okay, let's go to Larry. Tell us a little bit more about Zebrium. I'm interested always to ask a founder why you started the company. Rod touched on that a little bit. You guys have invented this concept of RCaaS. What does it mean? What problems does it solve, and how does it solve the problem? Let's get into it. >> Yeah. Hey, thanks, Dave. So I think when you said, you know, who's automating the observer, that that's a great way to think about it because what observability really means is it's a property of a system that means you can see into it. You can observe the internal state and that makes it easier to troubleshoot, right? But the problem is if it's too complicated, you just push the bottleneck up to your eyeball. There's only so much a person can filter through manually, right? And I love the way you put that. So that's a great way to think about it is automating the observer. Now, of course, it means that, you know, you reduce your MTTR, you meet your service level objectives, all that stuff, you improve customer experience. That's all true, but it's important to step back and realize like we have cracked a real nut here. People have been trying to figure out how to automate this part of sort of the troubleshooting experience, this human part of finding the root cause indicators for a long time. And until Zebrium came along, I would argue, no one's really done it right. So, you know, I think it's also important you know, as we step back, we can probably look forward five to 10 years and say, everyone's going to look back and say how did we do all this manually? You're going to see this sort of last mile of observability and troubleshooting is going to be automated everywhere because otherwise, you know, people are just... They're not going to be able to scale their business. So, you know, I think one more thing that's important to point out is, you know, I think Zebrium, you know, it's one thing to have the technology but we've learned we need to deliver it right where people are today. You can't just expect people to dive into a new tool. So, you know, we're looking at, you know, if you look at Zebrium, you'll put us on your dashboard and we don't care what kind of a dashboard it is. It could be, you know Datadog, New Relic, Elastic, Dynatrace, Grafana AppDynamics, ScienceLogic, we don't care. You know, they're all our friends. So we're more interested in getting to that root cause than trying to fight, you know, these incumbents and all that stuff. Yep. >> Yeah. So, interesting. Again, another analogy I think about. You know, you talked about automation. If we're to look back and say this is what... We're never going to do this again, it's like provisioning loans. Nobody provisions loans anymore, it's all automated. >> Larry: (chuckling) That's right. >> So Larry, I'll stay with you, then the skeptic in me says, this sounds amazing, but if I, you know... It might be too good to be true. Tell us how it works. >> Larry: (chuckling) Yeah. So that's interesting. So Cisco came along and they were equally skeptical. So what they did was they took a couple of months and they did a very detailed study. And they got together 192 incidents across four product lines, where they knew that the root cause was in the logs. And they knew what that root cause was because they had had their best engineers, you know work on those cases and take detailed notes of the incidents that had taken place. And so they ran that data through the Zebrium software. And what they found was that in more than 95% of those incidents, Zebrium reflected the correct root cause indicators at the correct time. Like that blew us away. When we saw that kind of evidence, Dave, I have to tell you, everyone was just jumping up and down. It was like, you know, it was like the Apollo command center, you know when they finally, you know, touchdown on the moon kind of thing. So, you know, it's really an exciting point in time to be at the company, like just seeing everything finally being proven out according to this vision. I'm going to tell you one more story which is actually one of my favorites, because we got a chance to work with Seagate Lyve Cloud. So they're, you know, a hyper modern, you know, SaaS business, they're an S3 competitor. Zoom has their files stored on Lyve Cloud, you know, to let you know who they are. So essentially, what happened was they were in alpha, their early access, and they had an outage, and it was pretty bad. I mean, it went on for longer than a day, actually, before they were completely restored. And it was, you know, fortunately for them, it was early access. So no one was expecting, you know, uptime, you know, service level objectives and so on. But they were scared, because they realized, if something like this happens in production, you know, they're screwed. So what they did was they saw Zebrium. They went and did some research, they saw Zebrium. They went in a staging environment, recreated the exact (indistinct) that they had had. And what they saw was immediately, Zebrium pops up a root cause report that tells them exactly the root cause that they took over a day to find. These are the kind of stories that let us know we're onto something transformational. >> Dave: Yeah. That's great. I mean, you guys are jumping up and down, I'm sure. We're going to hear from Cisco later. I bet you, they were jumping up and down too because they didn't have to do all that heavy lifting anymore. So Rod, Larry's just sort of implying that, or actually, you guys both talked about that your tool is agnostic. So how does one actually use the service? How do I deploy it? >> Yeah. So let me step back. So when we talk about logs right? Like, you know, all these bread crumbs being in logs and everything else? So, you know, they are a great wealth of you know, information, but people hate dealing with them. I mean, they hate having to go in and figure out what log to look at. In fact, you know, we had one of our... Or we've heard from several of our customers now prior to using Zebrium, when they, you know, have some issue, and they know there's something wrong, something on their dashboard has told them that something's wrong, maybe a metric has, you know, taken a blip or something's happened that they know there's a problem. We've heard from them that it can take like a number of hours just to get to the right set of logs, like figuring out over these hundreds of services where the logs are, to get to them, maybe searching in a log manager. Just to get into the right context, even, can take hours. So, you know, that's obviously the problem we solve but, you know, we don't want them just looking at logs. I mean, you know, we don't want to put them back in the thing they don't like doing because people don't do that. They don't like doing it. So we put it up on the dashboard. So if something is going wrong with your metrics and that's the indicator, or maybe it's something with tracing that you're sort of digging through that you know something's wrong, we will be right on that same dashboard. So we're deployed as a SaaS service. You send us your logs, you click on one of our integrations and we integrate with all these tools that Larry's talked about. And when we detect anything that is a root cause report, it will show up on your dashboard in the same timeline as those blips in your metrics. So when you see something going wrong and you know there's an issue, take a look at the portion of your dashboard that is us, and we're going to tell you why. We're going to get you to the why that went wrong. No other work could be... You can, you know, also click down and click through to us so that you land up in our portal, if you want to do some more digging around, if you need to or whatever, maybe to get some context what have you, but it's fair that if you ever need to do that, the answer should be right there on your dashboard. And that that's how we expect people to use it. We don't want them digging in logs and going through things, we want it to be right in their workflow. >> Great. Thank you, Larry. So Rod, we talked about Cisco. We're going to hear more from them in a moment in Seagate. I would think this is like a perfect solution for a SaaS provider, anybody doing AI ops. Do you have some examples of those types of firms leaning into this? >> Rod: Yeah, a couple of great ones. Well, I mean, we've got many of them, but a couple that I'll touch on. We have an actual AI ops company that was looking for, you know, sort of some complimentary technology and so on. And so they decided to just put us through our paces by having one of their own SREs sign up for our service in our SaaS environment, and send the logs from their system to us, you know, and just see how we did. So it turned out we ended up talking back to this SRE like a week after he had installed the product, you know signed up and then, you know, started sending us logs. And, you know, he was hewing and hawing, saying that he was busy, like every SRE is, and that he didn't have a chance to really do much with us yet. And, you know, we were just, you know, having this conversation on the phone, and he comes to tell us that, yeah I've been busy because we had this, you know, terrible outage, like, you know, five days ago. And we said like, "Okay did you actually look on the Zebrium dashboard?" (chuckles) And he goes, "You know what? I didn't even think to do it yet. I mean, I'd just been so busy and frazzled." So we have an integration with that company, he hadn't put that integration in, so it wasn't in his dashboard yet, but it was certainly on ours. So he went there, and he looks and he looks on the day, you know, on the time range of when he had had this incident. And right at the very top of the page on our portal was that incident with that root cause. And he was flabbergasted. It literally would've saved him hours and hours and hours. They had this issue going on for over 24 hours. And we had the answer right there in five minutes, and it was crazy. And we get that kind of stories. It's just like the Seagate one. If you use us and you have a problem, we're going to detect it. And you're going to hear from Cisco how successful we are at detecting things. I mean, it'll be there when you have a problem. In SaaS companies, you know, one of our customers is Alchera. They do cost optimizations for cloud properties, you know, for AWS optimization, Google, Google cloud, and so on. But they use our software, and they have a lot of interaction, obviously with these cloud vendors and the APIs of those cloud vendors. So, you know, in order to figure out your costing at AWS, they're using all those APIs. So it turned out, you know, they had some issue where their services were breaking. And we had that root cause report right on the screen, again within five minutes, that was pointing to an API problem with Google. And they had changed one of their APIs and Alchera was not aware of it. So their stuff was breaking because of a change downstream that we had caught. And I'll just tell you one last one because it's somewhat related to one of these cloud vendors. You know, it was a big cloud vendor who had an outage a couple of months ago. And it's interesting because, you know, a lot of our customers will set up shared Slack channels with us, where we're monitoring or seeing their incidents as well as they are. So we get a little Slack representation of the incident that we detected for them or the root cause that we detected for them, and that's in a shared community channel. So we could see this happening when that AWS outage happened. We could see our customers getting impacted by that AWS outage, and the root cause of what was going on there in AWS that was impacting our customers that was showing up in our incidents. Now we didn't obviously, you know, have the very root cause of what was going on in AWS, per se but we were getting to the root cause of why our customer's applications were failing. And that was because of issues going on at AWS. >> Very interesting. I mean, I think one of your biggest challenges is going to be getting people's attention because these SREs are so busy, their hair's on fire. >> Rod: That's it. Right. (chuckling). You know, when you say, hey, (indistinct). >> I tell you, if you get their attention, they love it. I mean, this AI ops company, I didn't even tell you the punchline there, but, you know, they had this incident that occurred that we found. And quite literally, the next week, they ended up signing up as a paid customer. So... >> Dave: that's great. And Larry, to give you the last word. I mean, you know, Rod was talking about, you know, changes in APIs and you know, there's still a lot of scripts out there. You guys, if I understand it correctly, run both as a service in the cloud and you can run on-prem, which is important because there's a lot of sensitive information in logs that people are trying not to leave. >> Larry: That's right. Absolutely. >> Dave: But close it out here. >> Yeah. I mean, that's right, you can run it on-prem. Just like we run it in our cloud, you can run it in your cloud or on your own infrastructure. Now that's all true. You know, I think the one hurdle now that we have left as a company is getting the word out and getting people to believe that this is actually possible and try it for themselves. You don't believe it, do a POC, try it yourself. And you know, people have become so jaded by the lack of, you know, real, sort of, innovation in the software industry for the last 10 years that it's hard to get people to... But guys, you got to give it a shot, I'm telling you. I'm telling you right now, it works. And you'll hear more about that from one of our customers in a minute. >> All right guys, thanks so much. Great story. Really appreciate you sharing. >> Thank you. >> Yeah. Thanks Dave. Appreciate the time. >> Okay. In a moment, we're going to hear from Cisco who is the customer in this case example and a company that has... Look, they have quite an impressive suite of observability tooling, and they've done a pretty compelling proof of concept with Zebrium using real data on some Cisco products that you've heard of, like WebEx. So stay tuned and learn about how you can really take advantage of this new technology called Root Cause As A Service. You're watching theCube, the leader in enterprise and emerging tech coverage. (upbeat music)

(upbeat music) >> Okay, we're back with Atri Basu who is Cisco's resident philosopher who also holds a master's in computer science. We're going to have to unpack that a little bit. And Necati Cehreli, who's technical lead at Cisco. Welcome, guys. Thanks for coming on theCUBE. >> Happy to be here. >> Thanks a lot. >> All right, let's get into it. We want you to explain how Cisco validated the Zebrium technology and the proof points that you have that it actually works as advertised. So first Atri, first tell us about Cisco TAC. What does Cisco TAC do? >> So TAC is otherwise it's an acronym for Technical Assistance Center, is Cisco's support arm, the support organization. And the risk of sounding like I'm spouting a corporate line. The easiest way to summarize what TAC does is provide world class support to Cisco customers. What that means is we have about 8,000 engineers worldwide and any of our Cisco customers can either go on our web portal or call us to open a support request. And we get about 2.2 million of these support requests a year. And what these support requests are, are essentially the customer will describe something that they need done some networking goal that they have that they want to accomplish. And then it's TACs job to make sure that that goal does get accomplished. Now, it could be something like they're having trouble with an existing network solution and it's not working as expected or it could be that they're integrating with a new solution. They're, you know, upgrading devices maybe there's a hardware failure anything really to do with networking support and, you know the customer's network goals. If they open up a case for testing for help then TACs job is to respond and make sure the customer's, you know questions and requirements are met. About 44% of these support requests are usually trivial and, you know can be solved within a call or within a day. But the rest of TAC cases really involve getting into the network device, looking at logs. It's a very technical role. It's a very technical job. You need to be conversed with network solutions, their designs, protocols, et cetera. >> Wow. So 56% non-trivial. And so I would imagine you spend a lot of time digging through logs. Is that true? Can you quantify that like, you know, every month how much time you spend digging through logs and is that a pain point? >> Yeah, it's interesting you asked that because when we started on this journey to augment our support engineers workflow with Zebrium solution, one of the things that we did was we went out and asked our engineers what their experience was like doing log analysis. And the anecdotal evidence was that on average an engineer will spend three out of their eight hours reviewing logs either online or offline. So what that means is either with the customer live on a WebEx, they're going to be going over logs, network, state information, et cetera or they're going to do it offline where the customer sends them the logs it's attached to a, you know, a service request and they review it and try to figure out what's going on and provide the customer with information. So it's a very large chunk of our day. You know, I said 8,000 plus engineers and so three hours a day that's 24,000 man hours a day spent on log analysis. Now the struggle with logs or analyzing logs is there by out of necessity, logs are very contrite. They try to pack a lot of information in a very little space. And this is for performance reasons, storage reasons, et cetera, but the side effect of that is they're very esoteric. So they're hard to read if you're not conversant if you're not the developer who wrote these logs or you aren't doing code deep dives. And you're looking at where this logs getting printed and things like that, it may not be immediately obvious or even after a little while it may not be obvious what that log line means or how it correlates to whatever problem you're troubleshooting. So it requires tenure. It requires, you know, like I was saying before it requires a lot of knowledge about the protocol what's expected because when you're doing log analysis what you're really looking for is a needle in a haystack. You're looking for that one anomalous event, that single thing that tells you this shouldn't have happened, and this was a problem right. Now doing that kind of anomaly detection requires you to know what is normal. It requires, you know, what the baseline is. And that requires a very in depth understanding of, you know the state changes for that network solution or product. So it requires time to near and expertise to do well. And it takes a lot of time even when you have that kind of expertise. >> Wow. So thank you, Atri. And Necati, that's almost two days a week for a technical resource. That's not inexpensive. So what was Cisco looking for to sort of help with this and how'd you stumble upon Zebrium? >> Yeah, so, we have our internal automation system which has been running more than a decade now. And what happens is when a customer attach log bundle or diagnostic bundle into the service request we take that from the Sr we analyze it and we represent some kind of information. You know, it can be alerts or some tables, some graph, to the engineer, so they can, you know troubleshoot this particular issue. This is an incredible system, but it comes with its own challenges around maintenance to keep it up to date and relevant with Cisco's new products or a new version of a product, new defects, new issues and all kind of things. And when I mean with those challenges are let's say Cisco comes up with a product today. We need to come together with those engineers. We need to figure out how this bundle works, how it's structured out. We need to select individual logs, which are relevant and then start modeling these logs and get some values out of those logs, using PaaS or some rag access to come to a level that we can consume the logs. And then people start writing rules on top of that abstraction. So people can say in this log I'm seeing this value together with this other value in another log, maybe I'm hitting this particular defect. So that's how it works. And if you look at it, the abstraction it can fail the next time. And the next release when the development or engineer decides to change that log line which you write that rag X or we can come up with a new version which we completely change the services or processes then whatever you have wrote needs to be re-written for the new service. And we see that a lot with products, like for instance, WebEx where you have a very short release cycle that things can change maybe the next week with a new release. So whatever you are writing, especially for that abstraction and for those rules are maybe not relevant with that new release. With that being said we have a incredible rule creation process and governance process around it which starts with maybe a defect. And then it takes it to a level where we have an automation in place. But if you look at it, this really ties to human bandwidth. And our engineers are really busy working on you know, customer facing, working on issues daily and sometimes creating news rules or these PaaS are not their biggest priorities so they can be delayed a bit. So we have this delay between a new issue being identified to a level where we have the automation to detect it next time that some customer faces it. So with all these questions and with all challenges in mind we start looking into ways of actually how we can automate these automation. So these things that we are doing manually how we can move it a bit further and automate. And we had actually a couple of things in mind that we were looking for and this being one of them being this has to be product agnostic. Like if Cisco comes up with a product tomorrow I should be able to take it logs without writing, you know, complex regs, PaaS, whatever and deploy it into this system. So it can embrace our logs and make sense of it. And we wanted this platform to be unsupervised. So none of the engineers need to create rules, you know, label logs, this is bad, this is good. Or train the system like which requires a lot of computational power. And the other most important thing for us was we wanted this to be not noisy at all because what happens with noises when your level of false positives really high your engineers start ignoring the good things between that noise. So they start the next time, you know thinking that this thing will not be relevant. So we want something with a lot more less noise. And ultimately we wanted this new platform or new framework to be easily adaptable to our existing workflow. So this is where we started. We start looking into the, you know first of all, internally, if we can build this thing and also start researching it, and we came up to Zebrium actually Larry, one of the co-founders of Zebrium. We came upon his presentation where he clearly explained why this is different, how this works and it immediately clicked in and we said, okay, this is exactly what we were looking for. We dive deeper. We checked the block posts where Zebrium guys really explain everything very clearly there. They're really open about it. And most importantly, there is a button in their system. And so what happens usually with AI ML vendors is they have this button where you fill in your details and a sales guys call you back and you know, explains the system here. They were like, this is our trial system. We believe in the system you can just sign up and try it yourself. And that's what we did. We took one of our Cisco live DNA Center, wireless platforms. We start streaming logs out of it. And then we synthetically, you know, introduce errors like we broke things. And then we realized that Zebrium was really catching the errors perfectly. And on top of that, it was really quiet unless you are really breaking something. And the other thing we realized was during that first trial is Zebrium was actually bringing a lot of context on top of the logs. During those failures, we worked with couple of technical leaders and they said, "Okay if this failure happens I'm expecting this individual log to be there." And we found out with Zebrium apart from that individual log there were a lot of other things which gives a bit more context around the root cause, which was great. And that's where we wanted to take it to the next level. Yeah. >> Okay. So, you know, a couple things to unpack there. I mean, you have the dart board behind you which is kind of interesting, 'cause a lot of times it's like throwing darts at the board to try to figure this stuff out. But to your other point, Cisco actually has some pretty rich tools with AppD and doing observability and you've made acquisitions like thousand eyes. And like you said, I'm presuming you got to eat your own dog food or drink your own champagne. And so you've got to be tools agnostic. And when I first heard about Zebrium, I was like wait a minute. Really? I was kind of skeptical. I've heard this before. You're telling me all I need is plain text and a timestamp. And you got my problem solved. So, and I understand that you guys said, okay let's run a POC. Let's see if we can cut that from, let's say two days a week down to one day, a week. In other words, 50%, let's see if we can automate 50% of the root cause analysis. And so you funded a POC. How did you test it? You put, you know, synthetic, you know errors and problems in there, but how did you test that, it actually works Necati? >> Yeah. So we wanted to take it to the next level which is meaning that we wanted to back test is with existing SaaS. And we decided, you know, we chose four different products from four different verticals, data center security, collaboration, and enterprise networking. And we find out SaaS where the engineer put some kind of log in the resolution summary. So they closed the case. And in the summary of the SR, they put "I identified these log lines and they led me to the root cause" and we ingested those log bundles. And we tried to see if Zebrium can surface that exact same log line in their analysis. So we initially did it with archery ourself and after 50 tests or so we were really happy with the results. I mean, almost most of them we saw the log line that we were looking for but that was not enough. And we brought it of course to our management and they said, "Okay, let's try this with real users" because the log being there is one thing but the engineer reaching to that log is another take. So we wanted to make sure that when we put it in front of our users, our engineers, they can actually come to that log themselves because, you know, we know this platform so we can, you know make searches and find whatever we are looking for but we wanted to do that. So we extended our pilots to some selected engineers and they tested with their own SaaS. Also due some back testing for some SaaS which are closed in the past or recently. And with a sample set of, I guess, close to 200 SaaS we find out like majority of the time, almost 95% of the time the engineer could find the log they were looking for in Zebrium's analysis. >> Yeah. Okay. So you were looking for 50%, you got the 95%. And my understanding is you actually did it with four pretty well known Cisco products, WebEx client, DNA Center Identity services, engine ISE, and then UCS. Unified pursuit. So you use actual real data and that was kind of your proof point, but Atri, so that sounds pretty impressive. And have you put this into production now and what have you found? >> Well, yes, we've launched this with the four products that you mentioned. We're providing our TAC engineers with the ability, whenever a support bundle for that product gets attached to the support request. We are processing it, using sense and then providing that sense analysis to the TAC engineer for their review. >> So are you seeing the results in production? I mean, are you actually able to reclaim that time that people are spending? I mean, it was literally almost two days a week down to you know, a part of a day, is that what you're seeing in production and what are you able to do with that extra time and people getting their weekends back? Are you putting 'em on more strategic tasks? How are you handling that? >> Yeah. So what we're seeing is, and I can tell you from my own personal experience using this tool that troubleshooting any one of the cases, I don't take more than 15 to 20 minutes to go through the Zebrium report. And I know within that time either what the root causes or I know that Zebrium doesn't have the information that I need to solve this particular case. So we've definitely seen, well it's been very hard to measure exactly how much time we've saved per engineer, right? Again, anecdotally, what we've heard from our users is that out of those three hours that they were spending per day, we're definitely able to reclaim at least one of those hours and what even more importantly, you know, what the kind of feedback that we've gotten in terms of I think one statement that really summarizes how Zebrium's impacted our workflow was from one of our users. And they said, "Well, you know, until you provide us with this tool, log analysis was a very black and white affair, but now it's become really colorful." And I mean, if you think about it log analysis is indeed black and white. You're looking at it on a terminal screen where the background is black and the text is white, or you're looking at it as a text where the background is white and the text is black, but what they're really trying to say is there are hardly any visual cues that help you navigate these logs which are so esoteric, so dense, et cetera. But what Zebrium does is it provides a lot of color and context to the whole process. So now you're able to quickly get to, you know using their Word Cloud, using their interactive histogram, using the summaries of every incident. You're very quickly able to summarize what might be happening and what you need to look into. Like, what are the important aspects of this particular log bundle that might be relevant to you? So we've definitely seen that. A really great use case that kind of encapsulates all of this was very early on in our experiment. There was this support request that had been escalated to the business unit or the development team. And the TAC engineer had really, they had an intuition about what was going wrong because of their experience because of, you know the symptoms that they'd seen. They kind of had an idea but they weren't able to convince the development team because they weren't able to find any evidence to back up what they thought was happening. And it was entirely happenstance that I happened to pick up that case and did an analysis using Zebrium. And then I sat down with a TAC engineer and we were very quickly within 15 minutes we were able to get down to the exact sequence of events that highlighted what the customer thought was happening, evidence of what the sorry not the customer what the TAC engineer thought was a root cause. And then we were able to share that evidence with our business unit and, you know redirect their resources so that we could chase down what the problem was. And that that really shows you how that color and context helps in log analysis. >> Interesting. You know, we do a fair amount of work in theCUBE in the RPA space, the robotic process automation and the narrative in the press when our RPA first started taking off was, oh, it's, you know machines replacing humans, or we're going to lose jobs. And what actually happened was people were just eliminating mundane tasks and the employees actually very happy about it. But what my question to you is was there ever a reticence amongst your team? Like, oh, wow, I'm going to lose my job if the machine's going to replace me or have you found that people were excited about this and what's been the reaction amongst the team? >> Well, I think, you know, every automation and AI project has that immediate gut reaction of you're automating away our jobs and so forth. And there is initially there's a little bit of reticence but I mean, it's like you said once you start using the tool, you realize that it's not your job, that's getting automated away. It's just that your job's becoming a little easier to do and it's faster and more efficient. And you're able to get more done in less time. That's really what we're trying to accomplish here. At the end of the day, Zebrium will identify these incidents. They'll do the correlation, et cetera. But if you don't understand what you're reading then that information's useless to you. So you need the human you need the network expert to actually look at these incidents, but what we are able to skin away or get rid of is all of is all the fat that's involved in our process like without having to download the bundle, which, you know when it's many gigabytes in size and now we're working from home with the pandemic and everything, you're, you know pulling massive amounts of logs from the corporate network onto your local device that takes time and then opening it up, loading it in a text editor that takes time. All of these things are we're trying to get rid of. And instead we're trying to make it easier and quicker for you to find what you're looking for. So it's like you said, you take away the mundane you take away the difficulties and the slog but you don't really take away the work the work still needs to be done. >> Yeah, great. Guys, thanks so much appreciate you sharing your story. It's quite, quite fascinating. Really. Thank you for coming on. >> Thanks for having us. >> You're very welcome. >> Excellent. >> Okay. In a moment, I'll be back to wrap up with some final thoughts. This is Dave Vellante and you're watching theCUBE. (upbeat music)

(bright intro music) >> Full stack observability is all the rage today. As businesses lean in to digital, customer experience becomes ever more important, why? Well, it's obvious. Fickle consumers can switch brands in the blink of an eye or the click of a mouse. Technology companies have sprung into action, and the observability space is getting pretty crowded in an effort to simplify the process of figuring out the root cause of application performance problems without an army of PhDs and lab coats, also known as endlessly digging through logs, for example. We see decades-old software companies that have traditionally done monitoring or log analytics and/or application performance management stepping up their game. These established players, you know, they typically have deep feature sets and sometimes purpose built tools that attack one particular segment of the marketplace, and now, they're pivoting through M&A and some organic development trying to fill gaps in their portfolio, and then you got all these new entrants coming to the market claiming end to end visibility across the so-called modern cloud and now edge-native stacks. Meanwhile, cloud players are gaining traction and participating through a combination of native tooling combined with strong ecosystems to address this problem, but, you know, recent survey research from ETR confirms our thesis that no one company has at all. Here's the thing. Customers just want to figure out the root cause as quickly and efficiently as possible. It's one thing to observe the stack end to end, but the question is who is automating the observers? And that's why we're here today. Hello, my name is Dave Vellante, and welcome to this special "CUBE" presentation where we dig into root cause analysis and, specifically, how one company, Zebrium, is using unsupervised machine learning to detect anomalies and pinpoint root causes and delivering it as an automated service. In this session, we have two deep dives. First, we're going to dig into this exciting new field of RCA, root cause as a service, with two of the founders and technical experts behind Zebrium, and then we bring in two technical experts from Cisco, an early Zebrium customer who ran a POC with Zebrium's service, automating and identifying root cause problems within four very well established and well-known Cisco product lines including Webex client and UCS. I was pretty amazed at the results, and I think you'll be impressed as well. So thanks for being here. Let's get started with me right now is Larry Lancaster who's a founder and CTO of Zebrium, and he's joined by Rod Bagg who's a founder and Vice-President of Engineering at the company. Gents, welcome, thanks for coming on. >> Thanks. >> (indistinct). >> To be here. >> Great to be here. >> All right, Rod, talk to me. Talk to me about software downtime, what root cause means, all the buzzwords in your domain, MTTR and SLO, what do we need to know? >> Yeah, I mean, it's like you said. I mean, it's extremely important to our customers and to most businesses out there to drive up time and avoid as much downtime as possible. So, you know, when you think about it, all of these businesses, most companies nowadays, either their product is software and it's running, you know, running on the web, and that that's how you get a point click or their business depends on it and, you know, internal systems to drive their business and to run it. Now, when that is down, that is hugely impacting to them. So if you take a look, you know, way back, you know, 20, 30 years ago, software was simple. You know, there wasn't much to it. It was pretty monolithic, and maybe it took a couple of people to maintain it and keep it running. It wasn't really anything complicated about it. It was a single tenant piece of software. Today's software is so complicated, often running, you know, maybe hundreds of services to keep that or to actually implement what that software is doing. So as you point out, you know, enter the sort of observability space and the tools that are now in use to help monitor that software and make sure when something goes wrong, they know about it, but there's kind of an interesting stat around the observability space. So when you look at observability in the context or through the lens of the cost of downtime, it's really interesting. So observability tools are about a $20 billion market, okay? But the cost of downtime, even with that in place, is still hundreds of billions of dollars. So you're not taking much of a bite out of what the real problem is. You have to solve root cause and get to that fast. So it's all great to know that something went wrong, but you got to know why, and it it's our contention here that, you know, really, when you take a look at the observability space, you have metrics. That's a great tool. I mean, there's lots of great tools out there, you know, around metrics monitoring that's going to tell you when something went wrong. It's very rarely it's going to tell you why. Similarly for tracing, it's going to point you to where the issue is. It's going to take you through that stack and probably pinpoint where you're being, you know, where it's happening or where something is running slow potentially. So that's great, but again, the root cause of why it's happening is going to be buried in log files, and I can expand on that a little bit more, but, you know, when you're a software developer, and you're writing your software, those log files are a wealth of information. It's just a set of breadcrumbs that are littered with facts about how the software is behaving and why it's doing what it's doing or why it went wrong, and it's that that really gets you to the root cause very fast, and that's, our contention is that these software systems are so complex nowadays, and that the root cause is lying in those logs. So how do you get there fast? You know, we would contend that you better automate that or you're just doomed for failure, and that's where we come in. >> Great. >> Getting to that request. >> Thank you, Rod. You know, it's interesting. You talk about the $20 billion market. There's an analogy with security, right? We spend 80, $100 billion a year on securing our infrastructure, and yet we lose, probably, closer to a trillion dollars a year in breaches, and there's a similar analogy here. 20 billion could be 5x in downtime impacts or more. Okay, let's go to Larry. Tell us a little bit more about Zebrium. I'm interested always to ask a founder why you started the company. Rod touched on that a little bit. You guys have invented this concept of RCAs. What does it mean? What problems does it solve? And how does it solve the problem? Let's get into it. >> Yeah, hey, thanks, Dave. So I think when you said, you know, who's automating the observer? That's a great way to think about it because what observability really means is it's a property of a system that means you can see into it. You can observe the internal state, and that makes it easier to troubleshoot, right? But the problem is if it's too complicated, you just push the bottleneck up to your eyeball. There's only so much a person can filter through manually, right? And I love the way you put that. So that's a great way to think about it is automating the observer. Now, of course, it means that, you know, you reduce your MTTR, you meet your service level objectives, all that stuff, you improve customer experience, that's all true, but it's important to step back and realize like we have cracked a real nut here. People have been trying to figure out how to automate this part of sort of the troubleshooting experience, this human part of finding the root cause indicators for a long time, and until Zebrium came along, I would argue no one's really done it right. So, you know, I think it's also important, you know, as we step back, we can probably look forward five to 10 years and say, "Everyone's going to look back and say, 'How did we do all this manually?'" You're going to see this sort of last mile of observability and troubleshooting is going to be automated everywhere because otherwise, you know, people are just, they're not going to be able to scale their business. So, you know, I think one more thing that's important to point out is, you know, I think Zebrium, you know, it's one thing to have the technology, but we've learned we need to deliver it right where people are today. You can't just expect people to dive into a new tool. So, you know, we're looking at, you know, if you look at Zebrium, you'll put us on your dashboard, and we don't care what kind of a dashboard it is. It could be, you know, Datadog, New Relic, Elastic, Dynatrace, Grafana, AppDynamics, ScienceLogic, we don't care. You know, they're all our friends. So we're more interested in getting to that root cause than trying to fight, you know, these incumbents and all that stuff, yeah. >> Yeah, so interesting. Again, another analogy I think about, you know, you talked about automation, where to look back, and say, "This is what- We're never going to do this again." It's like provisioning LANs. Nobody provisioned LANs anymore. It's all automated. >> That's correct. >> So, Larry, stay with you. The skeptic in me says, "This sounds amazing," but if, you know, it probably too good to be true. Tell us how it works. >> Yeah, so that's interesting. So Cisco came along and they were equally skeptical. So what they did was they took a couple of months, and they did a very detailed study, and they got together 192 incidents across four product lines where they knew that the root cause was in the logs, and they knew what that root cause was because they'd had their best engineers, you know, work on those cases and take detailed notes of the incidents that had taken place, and so they ran that data through the Zebrium software, and what they found was that in more than 95% of those incidents, Zebrium reflected the correct root cause indicators at the correct time. Like that blew us away. When we saw that kind of evidence, Dave, I have to tell you, everyone was just jumping up and down. It was like, you know, it was like the Apollo Command Center, you know, when they finally, (Dave laughs) you know, touchdown on the moon kind of thing. So, you know, it's really exciting at a point in time to be at the company, like just seeing everything finally being proven out according to this vision. I'm going to tell you one more story, which is actually one of my favorites, because we got a chance to work with Seagate Lyve Cloud. So they're, you know, a hyper modern, you know, SaaS business. They're an S3 competitor. Zoom has their files stored on Lyve Cloud to give, you know, to let you know who they are. So, essentially, what happened was they were in alpha, in their early access, and they had an outage, and it was pretty bad. I mean, it went on for longer than a day, actually, before they were completely restored, and it was, you know, fortunately, for them, it was early access. So no one was expecting, you know, uptime, you know, service level objectives and so on, but they were scared because they realized if something like this happens in production, you know, they're screwed. So what they did was they saw Zebrium, they did some research, they saw Zebrium. They went in a staging environment, recreated the exact (indistinct) that they'd had, and what they saw was, immediately, Zebrium pops up a root cause report that tells them exactly the root cause that they took over a day to find. These are the kind of stories that let us know we're onto something transformational. >> Yeah, that's great. I mean, you guys are jumping up and down. I'm sure, we're going to hear from Cisco later. I bet you, they were jumping up and down, too, 'cause they didn't have to do all that heavy lifting anymore. So Rod, Larry's just sort of implying that or, actually, you guys both talked about that your tool's agnostic. So how does one actually use the service? How do I deploy it? >> Yeah, so let me step back. So when we talk about logs, right? Like, you know, all these red crumbs being in logs and everything else. So, you know, they are a great wealth of, you know, information, but people hate dealing with them. I mean, they hate having to go in and figure out what log to look at. In fact, you know, we had one of our, or we've heard from several of our customers now prior to using Zebrium, but when they're, you know, have some issue, and they know there's something wrong, something on their dashboard has told them that something's wrong, maybe a metrics is, you know, taken a blip or something's happened that they know there's a problem, we've heard from them that it can take like a number of hours just to get to the right set of logs, like figuring out over these hundreds of services where the logs are to get to them, maybe searching in a log manager, just to get into the right context even can take hours. So, you know, that's obviously the problem we solve, but, you know, we don't want them just looking at logs. I mean, you know, we don't want to put 'em back in the thing they don't like doing 'cause people don't do what they don't like doing. So we put it up on the dashboard. So if something is going wrong with your metrics, and that's the indicator or maybe it's something with tracing that you're sort of digging through now that you know something's wrong, we will be right on that same dashboard. So we're deployed as a SaaS service. You send us your logs. You click on one of our integrations, and we integrate with all these tools that Larry's talked about, and when we detect anything that is a root cause report, it will show up on your dashboard in the same timeline as those blips in your metrics. So when you see something going wrong, and you know there's an issue, take a look at the portion of your dashboard that is us, and we're going to tell you why. We're going to get you to the why that went wrong. Not no other work could be- You can, you know, also click down and click through to us so that you land up in our portal if you want to do some more digging around if you need to or whatever, maybe to get some context, what have you, but it's fair that you ever need to do that. The answer should be right there on your dashboard, and that's how we expect people to use it. We don't want them digging in logs and going through things. We want it to be right in their workflow. >> Great, thank you, Larry. So Rod, we talked about Cisco. We're going to hear more from them in a moment and Seagate. I would think this is like a perfect solution for a SaaS provider, anybody doing AIOps, do you have some examples of those types of firms leaning into this? >> Yeah, a couple of great, well, I mean, we got many of them, but couple that I'll touch on. We have an actual AIOps company that was looking for, you know, sort of some complimentary technology and so on, and so they decided to just put us through our paces by having one of their own SREs sign up for our service in our SaaS environment and send the logs from their system to us, you know, and just see how we did. So it turned out we ended up talking back to this SRE like a week after he had installed the product, you know, signed up, and then, you know, started sending us logs, and, you know, he was hemming and hawing saying that he was busy like, you know, like every SRE is, and that he didn't have a chance to really do much with us yet, and, you know, we just, you know, having this conversation on the phone, and he comes to tell us that, "Yeah, I've been busy because we had this, you know, terrible outage like, you know, five days ago," and we said like, "Okay, did you actually look on the Zebrium dashboard?" (laughs) And he goes, "You know what? I didn't even think to do it yet. I mean, I'd just been so busy and frazzled." So we have an integration with that company. He hadn't put that integration in so it wasn't in his dashboard yet, but it was certainly on ours. So he went there and he looks on the day like, you know, on the time range of when he had this incident, and right at the very top of the page on our portal was the incident with the root cause, and he was flabbergasted. It literally would've saved him hours and hours and hours. They had this issue going on for over 24 hours, and we had the answer right there in five minutes, and it was crazy, and we get that kind of story. It's just like the Seagate one. If you use us and you have a problem, we're going to detect it, and you're going to hear from Cisco how successful we are at detecting things. I mean, it'll be there when you have a problem. In SaaS companies, you know, one of our customers is Archera. They do cost optimizations for cloud properties, you know, for AWS optimization, Google cloud, and so on, but they use our software, and they have a lot of interaction, obviously, with these cloud vendors and the APIs of those cloud vendors. So, you know, in order to figure out you're costing at AWS, they're using all those APIs. So it turned out, you know, they had some issue where their services were breaking and we had that root cause report right on the screen, again, within five minutes that was pointing to an API problem with Google, and they had changed one of their APIs, and Archera was not aware of it. So their stuff was breaking because of a change downstream that we had caught, and I'll just tell you one last one because it's somewhat related to one of these cloud vendors of, you know, big cloud vendor who had an outage couple of months ago, and it's interesting because, you know, lot of our customers will set up shared Slack channels with us where we're monitoring or seeing their incidents as well as they are. So we get a little Slack representation of the incident that we detected for them or the root cause that we've detected for them, and that's in a shared community channel. So we could see this happening when that AWS outage happened. We could see our customers getting impacted by that AWS outage and the root cause of what was going on there in AWS that was impacting our customers, that was showing up in our incidents. Now, we didn't obviously, you know, have the very root cause of what was going on in AWS per se, but we were getting to the root cause of why our customer's applications were failing, and that was because of issues going on at AWS. >> Very interesting. I mean, I think one of your biggest challenge is going to be getting people's attention because these SREs is so busy, their hair's on fire. (all laughs) You know, he's like, "Hey, chap, I'm going to show you, look at this." >> I tell you. You get their attention, they love it. I mean, this AIOps company, I didn't even tell you the punchline there, but, you know, they had this incident that occurred that we found and, quite literally, the next week, they ended up signing up as a paid customer, so. >> That's great, and Larry, give you the last word. I mean, you know, Rod was talking about, you know, changes in APIs, and, you know, there's still a lot of scripts out there. You guys, if I understand it correctly, run both as a service in the cloud and you can run on-prem, which is important because there's a lot of sensitive information in logs and people don't want to leave. >> That's right, absolutely. >> But, yeah, close it out here. >> Yeah, I mean, you can, that's right, you can run it on-prem, just like we run it in our cloud. You can run it in your cloud or on your own infrastructure. Now, that's all true. You know, I think the one hurdle now that we have left as a company is getting the word out and getting people to believe that this is actually possible and try it for themselves. You don't believe it? Do a POC, try it yourself. And, you know, people have become so jaded by the lack of, you know, real sort of innovation in the software industry for the last 10 years that it's hard to get people to... But guys, you got to give it a shot. I'm telling you. I'm telling you right now, it works, and you'll hear more about that from one of our customers in a minute. >> Alright guys, thanks so much. Great story, really appreciate you sharing. >> Thank you. >> Yeah, thanks, Dave. Appreciate the time. >> Okay, in a moment, we're going to hear from Cisco who is the customer in this case example, and a company that is... Look, they have quite an impressive suite of observability tooling, and they've done a pretty compelling proof of concept with Zebrium using real data on some Cisco products that you've heard of like Webex. So stay tuned and learn about how you can really take advantage of this new technology called root cause as a service. You're watching "theCUBE", the leader in enterprise and emerging tech coverage. (bright outro music)

>>The introduction of the modern public cloud in the mid two thousands permanently changed the way we think about it at the heart of it. The cloud operating model attacked one of the biggest problems in enterprise infrastructure, human labor costs more than half of it, budgets were spent on people. And much of that effort added little or no differentiable value to the business. The automation of provisioning management, recovery optimization and decommissioning infrastructure resources has gone mainstream as organizations demand a cloud-like model across all their application infrastructure, irrespective of its physical location. This is not only cut costs, but it's also improved quality and reduced human error. Hello everyone. My name is Dave Vellante and welcome to simplifying hybrid cloud made possible by Cisco today, we're going to explore hybrid cloud as an operating model for organizations or the definition of cloud is expanding. Cloud is no longer an abstract set of remote services, you know, somewhere out in the clouds. >>No, it's an operating model that spans public cloud on premises infrastructure. And it's also moving to edge locations. This trend is happening at massive scale. While at the same time, preserving granular control of resources. It's an entirely new game where it managers must think differently to deal with this complexity. And the environment is constantly changing the growth and diversity of applications continues. And now we're living in a world where the workforce is remote hybrid work is now a permanent state and will be the dominant model. In fact, a recent survey of CIO is by enterprise technology. Research ETR indicates that organizations expect 36% of their workers will be operating in a hybrid mode splitting time between remote work and in office environments. This puts added pressure on the application infrastructure required to support these workers. The underlying technology must be more dynamic and adaptable to accommodate constant change. >>So the challenge for it managers is ensuring that modern applications can be run with a cloud-like experience that spans on-prem public cloud and edge locations. This is the future of it. Now today we have three segments where we're going to dig into these issues and trends surrounding hybrid cloud. First up is Didi Dasgupta, who will set the stage and share with us how Cisco is approaching this challenge. Next we're going to hear from Maneesh Agra wall and Darren Williams, who will help us unpack HyperFlex, which is Cisco's hyper-converged infrastructure offering. And finally, our third segment we'll drill into unified compute more than a decade ago. Cisco pioneered the concept of bringing together compute with networking in a single offering. Cisco frankly changed the legacy server market with UCS unified compute system. The X series is Cisco's next generation architecture for the coming decade, and we'll explore how it fits into the world of hybrid cloud and its role in simplifying the complexity that we just discussed. So thanks for being here. Let's go. >>Okay. Let's start things off. Gus is back on the cube to talk about how we're going to simplify hybrid cloud complexity. DD. Welcome. Good to see you again. >>Hey Dave, thanks for having me. Good to see you again. Yeah, >>Our pleasure here. Uh, look, let's start with big picture. Talk about the trends you're seeing from your customers. >>Well, I think first off every customer, these days is a public cloud customer. They do have their on-premise data centers, but um, every customer is looking to move workloads, use services, cloud native services from the public cloud. I think that's, that's one of the big things that we're seeing, um, while that is happening. We're also seeing a pretty dramatic evolution of the application landscape itself. You've got bare metal applications. You always have virtualized applications. Um, and then most modern applications are, um, are containerized and, you know, managed by Kubernetes. So I think we're seeing a big change in, uh, uh, in the application landscape as well, and probably, you know, triggered by the first two things that I mentioned, the execution venue of the applications, and then the applications themselves it's triggering a change in the it organizations in the development organizations and sort of not only how they work within their organizations, but how they work across, um, all of these different organizations. So I think those are some of the big things that, uh, that I hear about when I talk to customers. >>Well, so it's interesting. I often say Cisco kind of changed the game and in server and compute when it, when it developed the original UCS and you remember there were organizational considerations back then bringing together the server team and the networking team. And of course the bus storage team. And now you mentioned Kubernetes, that is a total game changer with regard to whole the application development process. So you have to think about a new strategy in that regard. So how have you evolved your strategy? What is your strategy to help customers simplify, accelerate their hybrid cloud journey in that context? >>No, I think you're right. Um, back to the origins of UCS, I mean, we widen the networking company, builder server, well, we just enabled with the best networking technology. So we do compute that and now doing something similar on the software, actually the software for our, um, for our and you know, we've been on this journey for about four years. Um, but the software is called intersite and, you know, we started out with intersite being just the element manager management software for Cisco's compute and hyperconverged devices. Um, but then we've evolved it over the last few years because we believe that the customer shouldn't have to manage a separate piece of software would do manage the hardware of the underlying hardware and then a separate tool to connect it to a public cloud. And then the third tool to do optimization, workload optimization or performance optimization or cost optimization, a fourth tool do now manage Kubernetes and not just in one cluster, one cloud, but multi cluster multicloud. >>They should not have to have a fifth tool that does go into observability. Anyway, I can go on and on, but you get the idea. We wanted to bring everything onto that same platform that manage their infrastructure, but it's also the platform that enables the simplicity of hybrid cloud operations, automation. It's the same platform on which you can use to manage the Kubernetes infrastructure, uh, Kubernetes clusters. I mean, whether it's on-prem or in the cloud. So overall that's the strategy, bring it to a single platform and a platform is a loaded word, but we'll get into that a little bit, uh, you know, in this, in this conversation, but that's the overall strategy simplify? >>Well, you know, we brought a platform, I, I like to say platform beats products, but you know, there was a day and you could still point to some examples today in the it industry where, Hey, another tool we can monetize that and another one to solve a different problem. We can monetize that. Uh, and so tell me more about how intersite came about. You obviously sat back, you saw what your customers were going through. You said we can do better. So w tell us the story there. >>Yeah, absolutely. So look, it started with, um, you know, three or four guys in getting in a room and saying, look, we've had this, you know, management software, UCS manager, UCS director, and these are just the Cisco's management, you know, uh, for our softwares, for our own platform. Then every company has their, their own flavor. We said, we took on this ball goal of like, we're not when we rewrite this or we improve on this, we're not going to just write another piece of software. We're going to create a cloud service, or we're going to create a SAS offering because the same is the infrastructure built by us, whether it's on networking or compute or on software, how do our customers use it? Well, they use it to write and run their applications, their SAS services, every customer, every customer, every company today is a software company. >>They live and die by how they work or don't. And so we were like, we want to eat our own dog food here, right? We want to deliver this as a SAS offering. And so that's how it started being on this journey for about four years, tens of thousands of customers. Um, but it was a pretty big boat patient because, you know, um, the big change with SAS is, is you're, uh, as you're familiar today is the job of now managing this, this piece of software is not on the customer, it's on the vendor, right? This can never go down. We have a release every Thursday, new capabilities, and we've learned so much along the way, whether it's around scalability, reliability, um, working with, uh, our own companies, security organizations on what can or cannot be in a SAS service. Um, so again, it's just been a wonderful journey, but, uh, I wanted to point out, we are in some ways eating our own dog food because we built a SAS application that helps other companies deliver their SAS applications. >>So Cisco, I look at Cisco's business model and I compete, I of course, compare it to other companies in the infrastructure business, and obviously a very profitable company or large company you're growing faster than, than, than most of the traditional competitors. And so that means that you have more to invest. You, you, you can, you can afford things like doing stock buybacks, and you can invest in R and D. You don't have to make those hard trade-offs that a lot of your competitors have to make. So It's never enough, right. Never enough. But, but, but in speaking of R and D and innovations that your intro introducing I'm specifically interested in, how are you dealing with innovations to help simplify hybrid cloud in the operations there and prove flexibility and things around cloud native initiatives as well? >>Absolutely. Absolutely. Well, look, I think one of the fundamentals where we're philosophically different from a lot of options that I see in the industry is we don't need to build everything ourselves. We don't, I just need to create a damn good platform with really good platform services, whether it's, you know, around, um, search ability, whether it's around logging, whether it's around, you know, access control, multi-tenants, I need to create a really good platform and make it open. I do not need to go on a shopping spree to buy 17 and a half companies, and then figure out how to stitch it all together. Cause it's, it's almost impossible if it's impossible for us as a vendor, it's, it's three times more difficult, but for the customer who then has to consume it. So that was the philosophical difference in how we went about building in our sites. >>We've created a harden platform that's, that's always on. Okay. And then you, then the magic starts happening. Then you get partners, whether it is, um, you know, infrastructure partners like, uh, you know, some of our storage partners like NetApp or your, you know, others who want their conversion infrastructure is also to be managed or are other SAS offerings and software vendors, um, who have now become partners. Like we do not, we did not write to Terraform, you know, but we partnered with Tashi and now, uh, you know, Terraform services available on the intercept platform. We did not write all the algorithms for workload optimization between a public cloud and on-prem, we partnered with a company called ergonomics. And so that's now an offering on the intercept platform. So that's where we're philosophically different and sort of, uh, you know, w how we have gone about this. >>And, uh, it actually dovetails well into some of the new things that I want to talk about today that we're announcing on the inner side platform where we're actually announcing the ability to attach and, and be able to manage Kubernetes clusters, which are not on prem. They're actually on AWS, on Azure, uh, soon coming on, uh, on GC, on, uh, on GKE as well. So it really doesn't matter. We're not telling a customer if you're comfortable building your applications and running Kubernetes clusters on, you know, in AWS or Azure, stay there, but in terms of monitoring, managing it, you can use in our site is since you're using it on prem, you can use that same piece of software to manage Kubernetes clusters in a public cloud, or even manage the end in, in a, in an easy to instance. So, >>So the fact that you could, you mentioned storage, pure net app. So it's intersite can manage that infrastructure. I remember the hot-seat deal. It caught my attention. And of course, a lot of companies want to partner with Cisco because you've got such a strong ecosystem, but I thought that was an interesting move Turbonomic. You mentioned. And now you're saying Kubernetes in the public cloud, so a lot different than it was 10 years ago. Um, so my last question is how do you see this hybrid cloud evolving? I mean, you had private cloud and you had public cloud, it was kind of a tug of war there. We see these, these, these two worlds coming together. How will that evolve over the next few years? >>Well, I think it's, it's the evolution of the model and really look at depending on, you know, how you're keeping time. But I think one thing has become very clear. Again, we may be eating our own dog food. I mean, innercise is a hybrid cloud SAS applications that we've learned. Some of these lessons ourselves. One thing is referred that customers are looking for a consistent model, whether it's on the edge, on the polo public cloud, on-prem no data center. It doesn't matter if they're looking for a consistent model for operations, for governings or upgrades, or they're looking for a consistent operating model. What my crystal ball doesn't mean. There's going to be the rise of more custom plugs. It's still going to be hybrid. So allegations will want to reside wherever it makes most sense for them, which is most as the data moving data is the most expensive thing. >>So it's going to be located with the data that's on the edge. We on the air colo public cloud doesn't matter, but, um, basically you're gonna see more custom clouds, more industry-specific clouds, you know, whether it's for finance or constipation or retail industry specific, I think sovereign is going to play a huge role. Uh, you know, today, if you look at the cloud providers, you know, American and Chinese companies that these, the rest of the world, when it goes to making, you know, a good digital citizens, they're they're people and, you know, whether it's, gonna play control, um, and then distributed cloud also on edge, um, is, is gonna be the next frontier. And so that's where we are trying to line up our strategy. And if I had to sum it up in one sentence, it's really your cloud, your way, every customer is on a different journey. They will have their choice of like workload data, um, you know, upgrading your liability concerns. That's really what, what we are trying to enable for our customers. >>Uh, you know, I think I agree with doing that custom clouds. And I think what you're seeing is you said every company is a software company. Every company is also becoming a cloud company. They're building their own abstraction layers. They're connecting their on-prem to their, to their public cloud. They're doing that. They're, they're doing that across clouds. And they're looking for companies like Cisco to do the hard work. It give me an infrastructure layer that I can build value on top of, because I'm going to take my financial services business to my cloud model or my healthcare business. I don't want to mess around with it. I'm not going to develop, you know, custom infrastructure like an Amazon does. I'm going to look to Cisco in your R and D to do that. Do you buy that? >>Absolutely. I think, again, it goes back back to what I was talking about with blacks. You got to get the world, uh, a solid open, flexible platform, and it's flexible in terms of the technology flexible in how they want to consume it at some customers are fine with a SAS software. What if I talk to, you know, my friends in the federal team now that does not work so how they want to consume it, they want to, you know, our perspective sovereignty, we talked about it. So, you know, job for an infrastructure vendor like ourselves is give the world an open platform, give them the knobs, give them the right API. Um, but the last thing I would mention is, you know, there's still a place for innovation in hardware. Some of my colleagues are gonna engage into some of those, um, you know, details, whether it's on our X series platform or HyperFlex. Um, but it's really, it's going to, it's going to be software defined to SAS service and then, you know, give the world and open rock-solid platform, >>Got to run on something. All right, thanks DDL. It was a pleasure to have you in the queue. Great to see you. You're welcome in a moment, I'll be back to dig into hyperconverged and where HyperFlex fits and how it may even help with addressing some of the supply chain challenges that we're seeing in the market today.

>>With me now or Maneesh outer wall, senior director of product management for a HyperFlex. It's Cisco at flash for all. Number four. I love that on Twitter and Darren Williams, the director of business development and sales for Cisco, Mr. HyperFlex at Mr. HyperFlex on Twitter. Thanks guys. Hey, we're going to talk about some news and in HyperFlex and what role it plays in accelerating the hybrid cloud journey. Gentlemen, welcome to the cube. Good to see you. >>Thanks David. >>Hi, Darren. Let's start with you. So for hybrid cloud, you got to have on-prem connection, right? So you got to have basically a private cloud. What are your thoughts on that? >>Yeah, we agree. You can't, you can't have a hybrid cloud without that private adamant. And you've got to have a strong foundation in terms of how you set up the, the whole benefit of the cloud model you build in, in terms of what you want to try and get back from the cloud. You need a strong foundation. High conversions provides that we see more and more customers requiring a private cloud in their building with hyper conversions in particular HyperFlex, Mexican bank, all that work. They need a good strong cloud operations model to be able to connect both the private and the public. And that's where we look at insight. We've got solution around that to be able to connect that around a SAS offering Nathan looks around simplified operations, give some optimization and also automation to bring both private and public together in that hybrid world. >>Darren let's stay with you for a minute. When you talk to your customers, what are they thinking these days? W when it comes to implementing hyper-converged infrastructure in both the enterprise and at the edge, what are they trying to achieve? >>So, so there's many things they're trying to achieve. My probably the most brutal, honest is they're trying to save money. That's probably the quickest answer, but I think they're trying to look at, in terms of simplicity, how can they remove laser components they've had before in their infrastructure, we see obviously collapsing of storage into hyperconversions and storage networking. And we got customers that have saved 80% worth of savings by doing that class into a hyper conversion infrastructure away from their three tier infrastructure, also about scalability. They don't know the end game. So they're looking about how they can size for what they know now and how they can grow that with hyper-conversion. It's very easy. It's one of the major factors and benefits of hyperconversions. They also obviously need performance and consistent performance. They don't want to compromise performance around their virtual machines when they want to run multiple workloads, they need that consistency all the way through. >>And then probably one of the biggest ones is that around the simplicity model is the management layer, ease of management to make it easier for their operations. And we've got customers that have told us they've saved 50% of costs in that operations model, deploying flex also around the time-savings. They make massive time savings, which they can reinvest in their infrastructure and their operations teams in being able to innovate and go forward. And then I think probably one of the biggest pieces where you've seen as people move away from the three tier architecture is the deployment elements. And the ease of deployment gets easy with hyper-converged, especially with edge edge is a major, key use case for us. And what our customers want to do is get the benefit of the data center at the edge without a big investment. They don't want to compromise on performance, and they want that simplicity in both management and employment. >>And we've seen our analyst recommendations around what their readers are telling them in terms of how management deployments key for it, operations teams and how much they're actually saving by deploying edge and taking the burden away when they deploy hyper conversions. And as I said, the savings elements, the key there, and again, not always, but obviously there's all case studies around about public cloud being quite expensive at times over time for the wrong workloads. So by bringing them back, people could make savings. And we again have customers that have made 50% savings over three years compared to their public cloud usage. So I'd say that's the key things that customers are looking for. Yeah. >>Great. Thank you for that, Darren, uh, Monisha, we have some hard news. You've been working a lot on evolving the hyper flex line. What's the big news that you've just announced. >>Yeah. Thanks Dave. Um, so there are several things that we are seeing today. The first one is a new offer, um, called HyperFlex express. This is, uh, you know, Cisco intersite lend and Cisco intersect managed it HyperFlex configurations that we feel are the fastest spot to hybrid cloud. The second is we're expanding our service portfolio by adding support for each X on EMD rack, uh, UCS M D rack. And the code is a new capability that we're introducing that we calling, um, local and containerized witness and get, let me take a minute to explain what this is. This is a pretty nifty, uh, capability to optimize for, for an edge environments. So, you know, this leverage is the Cisco's ubiquitous presence, uh, of the networking, um, products that we have in the environments worldwide. So the smallest HyperFlex configuration that we have is, uh, configuration, which is primarily used in edge environments, think of a, you know, a backup woman or department store, or it might even be a smaller data center somewhere on the blue for these two, not two configurations. >>There is always a need for a third entity that, uh, you know, industry down for that is either a witness or an arbitrator. Uh, we had that for HyperFlex as well. And the problem that customers face is where do you host this witness? It cannot be on the cluster because it's the job of the witnesses to when the infrastructure is going. Now, it basically breaks, um, sort of, uh arbitrates which node gets to survive. So it needs to be outside of the cluster, but finding infrastructure, uh, to actually host this is a problem, especially in the edge environments where these are resource constrained environments. So what we've done is we've taken that test. We've converted it into a container or a form factor, and then qualified a very large slew of Cisco networking products that we have, right from ISR ESR, mixers, catalyst, industrial routers, uh, even, uh, even as we buy that can host host this witness, eliminating the need for you to find yet another piece of infrastructure are doing any, um, you know, Caden feeding or that infrastructure. You can host it on something that already exists in the environment. So those are the three things that we are announcing today. >>I want to ask you about HyperFlex express. You know, obviously the, the whole demand and supply chain is out of whack. Everybody's, you know, global supply chain issues are in the news, everybody's dealing with it. Can you expand on that a little bit more? Can, can HyperFlex express help customers respond to some of these issues? >>Yeah, indeed. The, um, you know, the primary motivation for HyperFlex express was indeed, uh, an idea that, uh, you know, one of the folks on my team had, we was to build a set of HyperFlex configurations that are, you know, would have a shorter lead time, but as we were brainstorming, we were actually able to tag on multiple other things and, uh, make sure that, uh, you know, that is in it for something in it for customers, for sales, as well as our partners. Uh, so for example, uh, you know, for customers, uh, we've been able to dramatically simplify the configuration and the install for HyperFlex express. These are still high-paced configurations, and you would at the end of it, get a HyperFlex cluster, but the part to that cluster is much, much, uh, simplifying. Uh, second is that we've added an flexibility where you can now deploy these, uh, these are data center configurations, but you can deploy these with, or without fabric interconnects, meaning you can deploy with your existing top of rack. >>Um, we've also added a, uh, attractive price point for these. And, uh, of course, uh, you know, these will have a better lead times because we made sure, uh, that, uh, you know, we are using components that are, um, that we have clear line of sight from a supply perspective for partner and sales. This is represents a high velocity sales motion, a foster doughnut around time, uh, and a frictionless sales motion for our distributors. Uh, this is actually a set of distinct friendly configurations, which they would find very easy to stock. And with a quick turnaround time, this would be very attractive for, uh, the disease as well. >>It's interesting Maneesh, I'm looking at some fresh survey data set more than 70% of the customers that were surveyed. This is ETR survey. Again, I mentioned them at the top more than the 70% said they had difficulty procuring a server hardware and networking was also a huge problem. So, so that's encouraging. Um, what about ministry, uh, AMD that's new for HyperFlex? What's that going to give customers that they couldn't get before? >>Yeah, Dave, so, uh, you know, in the short time that we've had UCS EMD direct support, we've had several record breaking benchmark results that we've published. So it's a, it's a, it's a powerful platform with a lot of performance in it. And HyperFlex, uh, you know, the differentiator that we've had from day one is that it is, it has the industry leading storage performance. So with this, we are going to get the masters compute together with the foster storage and this, we are logging that will, it'll basically unlock, you know, a, um, unprecedented level of performance and efficiency, but also unlock several new workloads, uh, that were previously locked out from the hyper-converged experience. >>Yeah. Cool. Um, so Darren, can you, can you give us an idea as to how HyperFlex is doing in the field? >>Sure, absolutely. So I've made, Maneesha been involved right from the Stein before it was called hype and we we've had a great journey and it's very exciting to see where we're taking, where we've been with the $10 year. So we have over 5,000 customers worldwide, and we're currently growing faster year over year than the market. Um, the majority of our customers are repeat buyers, which is always a good sign in terms of coming back when they've, uh, approved for technology and are comfortable with the technology. They repeat by expanded capacity, putting more workloads on they use in different use cases on that. And from an age perspective, more numbers of science. So really good endorsement, the technology, um, we get used across all verticals or segments, um, to house mission critical, uh, applications, as well as the, uh, traditional virtual server infrastructures, uh, and where the lifeblood of our customers around those mission critical customers. >>They want example, and I apologize for the worldwide audience, but this resonates with the American audiences, uh, the super bowl. So, uh, the like, uh, stadium that house, the soup, well actually has Cisco HyperFlex, right? In all the management services through, from the entire stadium for digital signage, 4k video distribution, and it's compete completely cashless. So if that were to break during the super bowl, that would have been a big, uh, news article, but it was run perfectly. We in the design of the solution were able to collapse down nearly 200 service into a few nodes, across a few racks and at a hundred, 120 virtual machines running the whole stadium without missing a heartbeat. And that is mission critical for you to run super bowl and not be on the front of the press afterwards for the wrong reasons. That's a win for us. So we really are really happy with the high place where it's going, what it's doing. And some of the use cases we're getting involved in very, very excited. >>He come on Darren Superbowl, NFL, that's, uh, that's international now. And you know, it's, it's dating London. Of course, I see the, the picture of the real football over your shoulder. But anyway, last question for minis. Give us a little roadmap. What's the future hold for HyperFlex. >>Yeah, so, you know, as Dan said, what data and I have been involved with type of flicks since the beginning, uh, but, uh, I think the best is we have to come. Uh, there are three main pillars for, uh, for HyperFlex. Um, one is intersite is central to our strategy. It provides a lot of customer benefit from a single pane of glass, um, management, but we are going to date this beyond the lifecycle management, which is a for HyperFlex, which is integrated. You're going to say today and element management, we're going to take it beyond that and start delivering customer value on the dimensions of AI ops, because intersect really provides us a ideal platform to gather slides from all the clusters across the globe, do AIML and do some predictive analysis with that and return it back as, uh, you know, customer value, um, actionable insights. >>So that is one, uh, the second is UCS expand the HyperFlex portfolio, go beyond UCS to third party server platforms and newer, uh, UCS, several platforms as well. But the highlight, there is one that I'm really, really excited about and think that there is a lot of potential in terms of the number of customers we can help is HX on X, CDs, uh, extra users. And other thing that'd be able to, uh, you know, uh, uh, get announcing a bunch of capabilities on in this particular launch. Uh, but each Axonics cities will have that by the end of this calendar year. And that should unlock with the flexibility of X of hosting, a multitude of workloads and the simplicity of HyperFlex. We were hoping that would bring a lot of benefits to new workloads, uh, that were locked out previously. And then the last thing is HyperFlex need a platform. >>This is the heart of the offering today, and you'll see the hyperlinks data platform itself. It's a distributed architecture, a unique architecture, primarily where we get our, you know, uh, they got bidding performance wrong. You'll see it get foster a more scalable, more resilient, and we'll optimize it for, uh, you know, containerized workloads, meaning it will get a granular container, a container, granular management capabilities and optimize for public cloud. So those are some things that we are, the team is busy working on, and we should see that come to fruition. I'm hoping that we'll be back at this forum in maybe before the end of the year and talking about some of these new capabilities. >>That's great. Thank you very much for that. Okay guys, we gotta leave it there. And, you know, Monisha was talking about the HX on X series. That's huge. Customers are gonna love that. And it's a great transition because in a moment I'll be back with VKS Ratana and Jim leech, and we're going to dig into X series. Some real serious engineering went into this platform and we're gonna explore what it all means. You're watching simplifying hybrid cloud on the cube. You're a leader in enterprise tech coverage.

(upbeat music) >> Welcome back to theCUBE special presentation, Simplifying Hybrid Cloud brought to you by Cisco. We're here with Vikas Ratna who's the director of product management for UCS at Cisco and James Leach, who is director of business development at Cisco. Gents welcome back to theCUBE, good to see you again. >> Hey, thanks for having us. >> Okay Jim, let's start. We know that when it comes to navigating a transition to hybrid cloud, it's a complicated situation for a lot of customers. And as organizations as they hit the pavement for their hybrid cloud journeys, what are the most common challenges that they face? What are they telling you? How Cisco specifically UCS helping them deal with these problems? >> Well, you know, first I think that's a, you know, that's a great question and, you know, customer-centric view is the way that we've taken, is kind of the approach we've taken from day one right? So I think that if you look at the challenges that we're solving for that our customers are facing, you could break them into just a few kind of broader buckets. The first would definitely be applications right? That's the, that's where the rubber meets your proverbial road with the customer, and I would say that, you know, what we're seeing is the challenges customers are facing within applications come from the way that applications have evolved. So what we're seeing now is more data-centric applications for example. Those require that we, you know, are able to move, and process large datasets really in real time. And the other aspect of applications I think that give our customers kind of some, you know, pose some challenges, would be around the fact that they're changing so quickly. So the application that exists today, or the day that they, you know, make a purchase of infrastructure to be able to support that application, that application is most likely changing so much more rapidly than the infrastructure can keep up with today. So, that creates some challenges around, you know, how do I build the infrastructure? How do I rightsize it without over provisioning for example? But also there's a need for some flexibility around life cycle and planning those purchase cycles based on the life cycle of the different hardware elements. And within the infrastructure, which I think is the second bucket of challenges, we see customers who are being forced to move away from the, like a modular or Blade approach which offers a lot of operational and consolidation benefits, and they have to move to something like a rack server model for some applications because of these needs that these data-centric applications have, and that creates a lot of, you know, opportunity for siloing infrastructure. And those silos in turn create multiple operating models within the, you know, a data center environment that, you know, again drive a lot of complexity. So that complexity is definitely the enemy here. And then finally I think life cycles. We're seeing this democratization of processing if you will, right? So it's no longer just CPU-focused, we have GPU, we have FPGA, we have, you know, things that are being done in storage and the fabrics that stitch them together, that are all changing rapidly and have very different life cycles. So, when those life cycles don't align, for a lot of our customers they see a challenge in how they can manage this, you know, these different life cycles and still make a purchase, without having to make too big of a compromise in one area or another because of the misalignment of life cycles. So that is a, you know, kind of the other bucket. And then finally I think management is huge, right? So management, you know, at its core is really rightsized for our customers and give them the most value when it meets the mark around scale and scope. You know, back in 2009 we weren't meeting that mark in the industry and UCS came about and took a management outside the chassis, right? We put it at the top of the rack and that worked great for the scale and scope we needed at that time, however, as things have changed, we're seeing a very new scale and scope needed right? So we're talking about a hybrid cloud world that has to manage across data centers, across clouds, and, you know, having to stitch things together for some of our customers poses a huge challenge. So there are tools for all of those operational pieces that touch the application, that touch the infrastructure but they're not the same tool. They tend to be disparate tools that have to be put together. >> Dave: All right. >> So our customers, you know, don't really enjoy being in the business of, you know, building their own tools so that creates a huge challenge. And one where I think that they really crave that full hybrid cloud stack that has that application visibility but also can reach down into the infrastructure. >> Right, you know, Jim I said in my open that you guys, Cisco had sort of changed the server game with the original UCS, but the X-Series is the next generation, the generation for the next decade which is really important 'cause you touched on a lot of things. These data-intensive workloads, alternative processors to sort of meet those needs, the whole cloud operating model and hybrid cloud has really changed so how is it going with with the X-Series? You made a big splash last year, what's the reception been in the field? >> Actually it's been great. You know, we're finding that customers can absolutely relate to our, you know, UCS X-Series story. I think that, you know, the main reason they relate to it is they helped create it, right? It was their feedback and their partnership that gave us really the, those problem areas, those areas that we could solve for the customer that actually add, you know, significant value. So, you know, since we brought UCS to market back in 2009, you know, we had this unique architectural paradigm that we created, and I think that created a product which was the fastest in Cisco history in terms of growth. What we're seeing now is X-Series is actually on a faster trajectory. So we're seeing a tremendous amount of uptake, we're seeing, you know, both in terms of, you know, the number of customers, but also more importantly, the number of workloads that our customers are using, and the types of workloads are growing, right? So we're growing this modular segment that exists, not just, you know, bringing customers onto a new product but we're actually bringing them into the product in the way that we had envisioned which is one infrastructure that can run any application into it seamlessly. So we're really excited to be growing this modular segment. I think the other piece, you know, that, you know, we judge ourselves is, you know, sort of not just within Cisco but also within the industry. And I think right now as a, you know, a great example, you know, our competitors have taken kind of swings and misses over the past five years at this, at a, you know, kind of the new next architecture, and we're seeing a tremendous amount of growth even faster than any of our competitors have seen when they announced something that was new to this space. So, I think that the ground-up work that we did is really paying off, and I think that what we're also seeing is it's not really a leapfrog game as it may have been in the past. X-Series is out in front today and, you know, we're extending that lead with some of the new features and capabilities we have. So we're delivering on the story that's already been resonating with customers, and, you know, we're pretty excited that we're seeing the results as well. So as our competitors hit walls, I think we're, you know, we're executing on the plan that we laid out back in June, when we launched X-Series to the world. And, you know, as we continue to do that, we're seeing, you know, again, tremendous uptake from our customers. >> So thank you for that Jim. So, Vikas I was just on Twitter just today actually talking about the gravitational pull, you've got the public clouds pulling CXOs one way, and you know, on-prem folks pulling the other way, and hybrid cloud so, organizations are struggling with a lot of different systems and architectures, and ways to do things. And I said that what they're trying to do is abstract all that complexity away and they need infrastructure to support that and I think your stated aim is really to try to help with that confusion with the X-Series right? I mean, so how so? Can you explain that? >> Sure, and that's the right, the context that you built up right there Dave. If you walk into enterprise data center you'll see plethora of compute systems spread all across because every application has its unique needs, and hence you find drive node, drive-dense system, memory-dense system, GPU-dense system, core-dense system, and variety of form factors, 1U, 2U, 4U, and every one of them typically come with, you know, variety of adapters and cables and so forth. This creates the siloness of resources. Fabric is brought, the adapter is brought, the power and cooling implications, the rack, you know, space challenges. And above all, the multiple management plane that they come up with which makes it very difficult for IT to have one common center policy, and enforce it all across the firmware, and software, and so forth. And then think about upgrade challenges of the siloness makes it even more complex as these go through the upgrade references of their own. As a result we observe quite a few of our customers, you know, really, seeing a slowness in their agility, and high burdened in the cost of overall ownership. This is where with the X-Series powered by Intersight, we have one simple goal. We want to make sure our customers get out of that complexities, they become more agile, and drive lower these issues. And we are delivering it by doing three things, three aspects of simplification. First, simplify their whole infrastructure by enabling them to run their entire workload on single infrastructure. An infrastructure which removes the siloness of form factor. An infrastructure which reduces the rightful footprint that is required. Infrastructure where power and cooling budgets are in the lower. Second, we want to simplify with, by delivering a cloud operating model. Where they can create the policy once across compute, network, storage, and deploy it all across. And third, we want to take away the pain they have by simplifying the process of upgrade, and any platform evolution that they're going to go through in the next two, three years. So that's where, the focus is on just driving down the simplicity, lowering down their issues. >> Oh, that's key. Less friction is always a good thing. Now of course, Vikas we heard from the HyperFlex guys earlier, they had news not to be outdone, you have hard news as well, what innovations are you announcing around X-Series today? >> Absolutely, so we are following up on the exciting X-Series announcement that we made in June last year Dave, and we are now introducing three innovation on X-Series with the goal of three things. First, expand the supported workload on X-Series. Second, take the performance to new levels. Third, dramatically reduce the complexities in the data center by driving down the number of adapters and cables that are needed. To that end, three new innovations are coming in. First, we are introducing the support for the GPU node using a cableless and very unique X Fabric architecture. This is the most elegant design to add the GPUs to the compute node in the modular form factor. Thereby our customers can now power in AI/ML workload, or any workload that need many more number of GPUs. Second, we are bringing in GPUs right onto the compute node. And thereby our customers can now fire up the accelerated VDI workload for example. And third, which is what you know, we are extremely proud about, is we are innovating again by introducing the 5th generation of our very popular Unified Fabric Technology. With the increased bandwidth that it brings in, coupled with the local drive capacity and densities that we have on the compute node, our customers can now fire up the big data workload, the HCI workload, the SDS workload, all these workloads that have historically not lived in the modular farm factor, can be run over there and benefit from the architectural benefits that we have. Second, with the announcement of fifth generation fabric we've become the only vendor to now finally enable 100 Gig end-to-end single port bandwidth, and there are multiple of those that are coming in there. And we are working very closely with our CI partners to deliver the benefit of this performance through our Cisco Validated Design to our CI franchise. And third, the innovations in the fifth gen fabric will again allow our customers to have fewer physical adapters, may it be ethernet adapter, may it be with fiber channel adapters, or may it be the other storage adapters, they've reduced it down and coupled with the reduction in the cable. So very, very excited about these three big announcements that we are making in the smart release. >> Great, a lot there, you guys have been busy, so thank you for that Vikas. So Jim you talked a little bit about the momentum that you have, customers are adopting, what problems are they telling you that X-Series addresses and how do they align with where they want to go in the future? >> That's a great question. I think if you go back to and think about some of the things that we mentioned before in terms of the problems that we originally set out to solve, we're seeing a lot of traction. So what Vikas mentioned I think is is really important, right? Those pieces that we just announced really enhanced that story and really move, again, to the, kind of to the next level of taking advantage of some of these, you know, problem solving for our customers. You know, if you look at, you know, I think Vikas mentioned accelerated VDI, that's a great example. These are where customers, you know, they need to have this dense compute, they need video acceleration, they need tight policy management, right? And they need to be able to deploy these systems anywhere in the world. Well, that's exactly what we're hitting on here with X-Series right now. We're hitting the market every, every single way, right? We have the highest compute config density that we can offer across the, you know, the very top end configurations of CPUs, and a lot of room to grow, we have the, you know, the premier cloud-based management you know, hybrid cloud suite in the industry right? So check there. We have the flexible GPU accelerators that you, that Vikas just talked about that we're announcing both on the system and also adding additional ones to the, through the use of the X Fabric, which is really, really critical to this launch as well, and, you know, I think finally the fifth generation of Fabric Interconnect, and Virtual Interface Card, and Intelligent Fabric Module go hand in hand in creating this 100 Gig end-to-end bandwidth story that we can move a lot of data. Again, you know, having all this performance is only as good as what we can get in and out of it right? So giving customers the ability to manage it anywhere, to be able to get the bandwidth that they need, to be able to get the accelerators that are flexible to, that it fit exactly their needs, this is huge, right? It solves a lot of the problems we can tick off right away. With the infrastructure as I mentioned, X Fabric is really critical here because it opens a lot of doors here, you know, we're talking about GPUs today, but in the future there are other elements that we can disaggregate like the GPUs that solve of these life cycle mismanagement issues, they solve issues around the form factor limitations. It solves all these issues for, like it does for GPU we can do that with storage or memory in the future. So that's going to be huge, right? This is disaggregation that actually delivers, right? It's not just a gimmicky bar trick here that we're doing, this is something that customers can really get value out of day one. And then finally, I think the, you know, the future readiness here, you know, we avoid saying future proof because we're kind of embracing the future here. We know that not only are the GPUs going to evolve, the CPUs are going to evolve, the drives, you know, the storage modules are going to evolve. All of these things are changing very rapidly, the fabric that stitches them together is critical and we know that we're just on the edge of some of the developments that are coming with CXL, with some of the PCI Express changes that are coming in the very near future, so we're ready to go. X, and the X Fabric is exactly the vehicle that's going to be able to deliver those technologies to our customers, right? Our customers are out there saying that, you know, they want to buy into something like X-Series that has all the operational benefits, but at the same time, they have to have the comfort in knowing that they're protected against being locked out of some technology that's coming in the future right? We want our customers to take these disruptive technologies and not be disrupted but use them to disrupt their competition as well. So we, you know, we're really excited about the pieces today, and I think it goes a long way towards continuing to tell the customer benefit story that X-Series brings, and, you know, again, you know, stay tuned because it's going to keep getting better as we go. >> Yeah, a lot of headroom for scale and the management piece is key there. Just have time for one more question Vikas, talk, give us some nuggets on the roadmap. What's next for X-Series that we can look forward to. >> Absolutely Dave. As we talked about and James also hinted, this is a future-ready architecture. A lot of focus and innovation that we are going through is about enabling our customers to seamlessly and painlessly adopt very disruptive hardware technologies that are coming up, no refund replace. And there we are looking into enabling the customer's journey as they transition from PCA in less than four to five to six, without rip and replace, as they embrace CXL without rip and replace, as they embrace the newer paradigm of computing through the disaggregated memory, disaggregated PCI or NVMe-based dense drives and so forth. We are also looking forward to X Fabric next generation which will allow dynamic assignment of GPUs anywhere within the chassis and much more. So this is again all about focusing on the innovation that will make the enterprise data center operations a lot more simpler, and drive down the TCO, by keeping them not only covered for today but also for future. So that's where some of the focus is on Dave. >> Okay, thank you guys, we'll leave it there, in a moment I'll have some closing thoughts. (bright upbeat music) We're seeing a major evolution perhaps even a bit of a revolution in the underlying infrastructure necessary to support hybrid work. Look, virtualizing compute and running general purpose workloads is something it figured out a long time ago. But just when you have it nailed down in the technology business, things change don't they? You can count on that. The cloud operating model has bled into on-premises locations, and is creating a new vision for the future, which we heard a lot about today. It's a vision that's turning into reality and it supports much more diverse and data-intensive workloads and alternative compute modes. It's one where flexibility is a watchword enabling change, attacking complexity, and bringing a management capability that allows for a granular management of resources at massive scale. I hope you've enjoyed this special presentation, remember all these videos are available on demand at thecube.net, and if you want to learn more please click on the information link. Thanks for watching Simplifying Hybrid Cloud brought to you by Cisco and theCUBE, your leader in enterprise tech coverage. This is Dave Vellante be well, and we'll see you next time. (upbeat music)

>> The introduction of the modern public cloud in the mid 2000s, permanently changed the way we think about IT. At the heart of it, the cloud operating model attacked one of the biggest problems in enterprise infrastructure, human labor costs. More than half of IT budgets were spent on people, and much of that effort added little or no differentiable value to the business. The automation of provisioning, management, recovery, optimization, and decommissioning infrastructure resources has gone mainstream as organizations demand a cloud-like model across all their application infrastructure, irrespective of its physical location. This has not only cut cost, but it's also improved quality and reduced human error. Hello everyone, my name is Dave Vellante and welcome to Simplifying Hybrid Cloud, made possible by Cisco. Today, we're going to explore Hybrid Cloud as an operating model for organizations. Now the definite of cloud is expanding. Cloud is no longer an abstract set of remote services, you know, somewhere out in the clouds. No, it's an operating model that spans public cloud, on-premises infrastructure, and it's also moving to edge locations. This trend is happening at massive scale. While at the same time, preserving granular control of resources. It's an entirely new game where IT managers must think differently to deal with this complexity. And the environment is constantly changing. The growth and diversity of applications continues. And now, we're living in a world where the workforce is remote. Hybrid work is now a permanent state and will be the dominant model. In fact, a recent survey of CIOs by Enterprise Technology Research, ETR, indicates that organizations expect 36% of their workers will be operating in a hybrid mode. Splitting time between remote work and in office environments. This puts added pressure on the application infrastructure required to support these workers. The underlying technology must be more dynamic and adaptable to accommodate constant change. So the challenge for IT managers is ensuring that modern applications can be run with a cloud-like experience that spans on-prem, public cloud, and edge locations. This is the future of IT. Now today, we have three segments where we're going to dig into these issues and trends surrounding Hybrid Cloud. First up, is DD Dasgupta, who will set the stage and share with us how Cisco is approaching this challenge. Next, we're going to hear from Manish Agarwal and Darren Williams, who will help us unpack HyperFlex which is Cisco's hyperconverged infrastructure offering. And finally, our third segment will drill into Unified Compute. More than a decade ago, Cisco pioneered the concept of bringing together compute with networking in a single offering. Cisco frankly, changed the legacy server market with UCS, Unified Compute System. The X-Series is Cisco's next generation architecture for the coming decade and we'll explore how it fits into the world of Hybrid Cloud, and its role in simplifying the complexity that we just discussed. So, thanks for being here. Let's go. (upbeat music playing) Okay, let's start things off. DD Dasgupta is back on theCUBE to talk about how we're going to simplify Hybrid Cloud complexity. DD welcome, good to see you again. >> Hey Dave, thanks for having me. Good to see you again. >> Yeah, our pleasure. Look, let's start with big picture. Talk about the trends you're seeing from your customers. >> Well, I think first off, every customer these days is a public cloud customer. They do have their on-premise data centers, but, every customer is looking to move workloads, new services, cloud native services from the public cloud. I think that's one of the big things that we're seeing. While that is happening, we're also seeing a pretty dramatic evolution of the application landscape itself. You've got, you know, bare metal applications, you always have virtualized applications, and then most modern applications are containerized, and, you know, managed by Kubernetes. So I think we're seeing a big change in, in the application landscape as well. And, probably, you know, triggered by the first two things that I mentioned, the execution venue of the applications, and then the applications themselves, it's triggering a change in the IT organizations in the development organizations and sort of not only how they work within their organizations, but how they work across all of these different organizations. So I think those are some of the big things that, that I hear about when I talk to customers. >> Well, so it's interesting. I often say Cisco kind of changed the game in server and compute when it developed the original UCS. And you remember there were organizational considerations back then bringing together the server team and the networking team and of course the storage team as well. And now you mentioned Kubernetes, that is a total game changer with regard to whole the application development process. So you have to think about a new strategy in that regard. So how have you evolved your strategy? What is your strategy to help customers simplify, accelerate their hybrid cloud journey in that context? >> No, I think you're right Dave, back to the origins of UCS and we, you know, why did a networking company build a server? Well, we just enabled with the best networking technologies so, would do compute better. And now, doing something similar on the software, actually the managing software for our hyperconvergence, for our, you know, Rack server, for our blade servers. And, you know, we've been on this journey for about four years. The software is called Intersight, and, you know, we started out with Intersight being just the element manager, the management software for Cisco's compute and hyperconverged devices. But then we've evolved it over the last few years because we believe that a customer shouldn't have to manage a separate piece of software, would do manage the hardware, the underlying hardware. And then a separate tool to connect it to a public cloud. And then a third tool to do optimization, workload optimization or performance optimization, or cost optimization. A fourth tool to now manage, you know, Kubernetes and like, not just in one cluster, one cloud, but multi-cluster, multi-cloud. They should not have to have a fifth tool that does, goes into observability anyway. I can go on and on, but you get the idea. We wanted to bring everything onto that same platform that manage their infrastructure. But it's also the platform that enables the simplicity of hybrid cloud operations, automation. It's the same platform on which you can use to manage the, the Kubernetes infrastructure, Kubernetes clusters, I mean, whether it's on-prem or in a cloud. So, overall that's the strategy. Bring it to a single platform, and a platform is a loaded word we'll get into that a little bit, you know, in this conversation, but, that's the overall strategy, simplify. >> Well, you know, you brought platform. I like to say platform beats products, but you know, there was a day, and you could still point to some examples today in the IT industry where, hey, another tool we can monetize that. And another one to solve a different problem, we can monetize that. And so, tell me more about how Intersight came about. You obviously sat back, you saw what your customers were going through, you said, "We can do better." So tell us the story there. >> Yeah, absolutely. So, look, it started with, you know, three or four guys in getting in a room and saying, "Look, we've had this, you know, management software, UCS manager, UCS director." And these are just the Cisco's management, you know, for our, softwares for our own platforms. And every company has their own flavor. We said, we took on this bold goal of like, we're not, when we rewrite this or we improve on this, we're not going to just write another piece of software. We're going to create a cloud service. Or we're going to create a SaaS offering. Because the same, the infrastructure built by us whether it's on networking or compute, or the cyber cloud software, how do our customers use it? Well, they use it to write and run their applications, their SaaS services, every customer, every customer, every company today is a software company. They live and die by how their applications work or don't. And so, we were like, "We want to eat our own dog food here," right? We want to deliver this as a SaaS offering. And so that's how it started, we've being on this journey for about four years, tens of thousands of customers. But it was a pretty big, bold ambition 'cause you know, the big change with SaaS as you're familiar Dave is, the job of now managing this piece of software, is not on the customer, it's on the vendor, right? This can never go down. We have a release every Thursday, new capabilities, and we've learned so much along the way, whether it's to announce scalability, reliability, working with, our own company's security organizations on what can or cannot be in a SaaS service. So again, it's been a wonderful journey, but, I wanted to point out, we are in some ways eating our own dog food 'cause we built a SaaS application that helps other companies deliver their SaaS applications. >> So Cisco, I look at Cisco's business model and I compare, of course compare it to other companies in the infrastructure business and, you're obviously a very profitable company, you're a large company, you're growing faster than most of the traditional competitors. And, so that means that you have more to invest. You, can afford things, like to you know, stock buybacks, and you can invest in R&D you don't have to make those hard trade offs that a lot of your competitors have to make, so-- >> You got to have a talk with my boss on the whole investment. >> Yeah, right. You'd never enough, right? Never enough. But in speaking of R&D and innovations that you're intro introducing, I'm specifically interested in, how are you dealing with innovations to help simplify hybrid cloud, the operations there, improve flexibility, and things around Cloud Native initiatives as well? >> Absolutely, absolutely. Well, look, I think, one of the fundamentals where we're kind of philosophically different from a lot of options that I see in the industry is, we don't need to build everything ourselves, we don't. I just need to create a damn good platform with really good platform services, whether it's, you know, around, searchability, whether it's around logging, whether it's around, you know, access control, multi-tenants. I need to create a really good platform, and make it open. I do not need to go on a shopping spree to buy 17 and 1/2 companies and then figure out how to stich it all together. 'Cause it's almost impossible. And if it's impossible for us as a vendor, it's three times more difficult for the customer who then has to consume it. So that was the philosophical difference and how we went about building Intersight. We've created a hardened platform that's always on, okay? And then you, then the magic starts happening. Then you get partners, whether it is, you know, infrastructure partners, like, you know, some of our storage partners like NetApp or PR, or you know, others, who want their conversion infrastructures also to be managed, or their other SaaS offerings and software vendors who have now become partners. Like we did not write Terraform, you know, but we partnered with Hashi and now, you know, Terraform service's available on the Intersight platform. We did not write all the algorithms for workload optimization between a public cloud and on-prem. We partner with a company called Turbonomic and so that's now an offering on the Intersight platform. So that's where we're philosophically different, in sort of, you know, how we have gone about this. And, it actually dovetails well into, some of the new things that I want to talk about today that we're announcing on the Intersight platform where we're actually announcing the ability to attach and be able to manage Kubernetes clusters which are not on-prem. They're actually on AWS, on Azure, soon coming on GC, on GKE as well. So it really doesn't matter. We're not telling a customer if you're comfortable building your applications and running Kubernetes clusters on, you know, in AWS or Azure, stay there. But in terms of monitoring, managing it, you can use Intersight, and since you're using it on-prem you can use that same piece of software to manage Kubernetes clusters in a public cloud. Or even manage DMS in a EC2 instance. So. >> Yeah so, the fact that you could, you mentioned Storage Pure, NetApp, so Intersight can manage that infrastructure. I remember the Hashi deal and I, it caught my attention. I mean, of course a lot of companies want to partner with Cisco 'cause you've got such a strong ecosystem, but I thought that was an interesting move, Turbonomic you mentioned. And now you're saying Kubernetes in the public cloud. So a lot different than it was 10 years ago. So my last question is, how do you see this hybrid cloud evolving? I mean, you had private cloud and you had public cloud, and it was kind of a tug of war there. We see these two worlds coming together. How will that evolve on for the next few years? >> Well, I think it's the evolution of the model and I, really look at Cloud, you know, 2.0 or 3.0, or depending on, you know, how you're keeping terms. But, I think one thing has become very clear again, we, we've be eating our own dog food, I mean, Intersight is a hybrid cloud SaaS application. So we've learned some of these lessons ourselves. One thing is for sure that the customers are looking for a consistent model, whether it's on the edge, on the COLO, public cloud, on-prem, no data center, it doesn't matter. They're looking for a consistent model for operations, for governance, for upgrades, for reliability. They're looking for a consistent operating model. What (indistinct) tells me I think there's going to be a rise of more custom clouds. It's still going to be hybrid, so applications will want to reside wherever it most makes most sense for them which is obviously data, 'cause you know, data is the most expensive thing. So it's going to be complicated with the data goes on the edge, will be on the edge, COLO, public cloud, doesn't matter. But, you're basically going to see more custom clouds, more industry specific clouds, you know, whether it's for finance, or transportation, or retail, industry specific, I think sovereignty is going to play a huge role, you know, today, if you look at the cloud provider there's a handful of, you know, American and Chinese companies, that leave the rest of the world out when it comes to making, you know, good digital citizens of their people and you know, whether it's data latency, data gravity, data sovereignty, I think that's going to play a huge role. Sovereignty's going to play a huge role. And the distributor cloud also called Edge, is going to be the next frontier. And so, that's where we are trying line up our strategy. And if I had to sum it up in one sentence, it's really, your cloud, your way. Every customer is on a different journey, they will have their choice of like workloads, data, you know, upgrade reliability concern. That's really what we are trying to enable for our customers. >> You know, I think I agree with you on that custom clouds. And I think what you're seeing is, you said every company is a software company. Every company is also becoming a cloud company. They're building their own abstraction layers, they're connecting their on-prem to their public cloud. They're doing that across clouds, and they're looking for companies like Cisco to do the hard work, and give me an infrastructure layer that I can build value on top of. 'Cause I'm going to take my financial services business to my cloud model, or my healthcare business. I don't want to mess around with, I'm not going to develop, you know, custom infrastructure like an Amazon does. I'm going to look to Cisco and your R&D to do that. Do you buy that? >> Absolutely. I think again, it goes back to what I was talking about with platform. You got to give the world a solid open, flexible platform. And flexible in terms of the technology, flexible in how they want to consume it. Some of our customers are fine with the SaaS, you know, software. But if I talk to, you know, my friends in the federal team, no, that does not work. And so, how they want to consume it, they want to, you know, (indistinct) you know, sovereignty we talked about. So, I think, you know, job for an infrastructure vendor like ourselves is to give the world a open platform, give them the knobs, give them the right API tool kit. But the last thing I will mention is, you know, there's still a place for innovation in hardware. And I think some of my colleagues are going to get into some of those, you know, details, whether it's on our X-Series, you know, platform or HyperFlex, but it's really, it's going to be software defined, it's a SaaS service and then, you know, give the world an open rock solid platform. >> Got to run on something All right, Thanks DD, always a pleasure to have you on the, theCUBE, great to see you. >> Thanks for having me. >> You're welcome. In a moment, I'll be back to dig into hyperconverged, and where HyperFlex fits, and how it may even help with addressing some of the supply chain challenges that we're seeing in the market today. >> It used to be all your infrastructure was managed here. But things got more complex in distributing, and now IT operations need to be managed everywhere. But what if you could manage everywhere from somewhere? One scalable place that brings together your teams, technology, and operations. Both on-prem and in the cloud. One automated place that provides full stack visibility to help you optimize performance and stay ahead of problems. One secure place where everyone can work better, faster, and seamlessly together. That's the Cisco Intersight cloud operations platform. The time saving, cost reducing, risk managing solution for your whole IT environment, now and into the future of this ever-changing world of IT. (upbeat music) >> With me now are Manish Agarwal, senior director of product management for HyperFlex at Cisco, @flash4all, number four, I love that, on Twitter. And Darren Williams, the director of business development and sales for Cisco. MrHyperFlex, @MrHyperFlex on Twitter. Thanks guys. Hey, we're going to talk about some news and HyperFlex, and what role it plays in accelerating the hybrid cloud journey. Gentlemen, welcome to theCUBE, good to see you. >> Thanks a lot Dave. >> Thanks Dave. >> All right Darren, let's start with you. So, for a hybrid cloud, you got to have on-prem connection, right? So, you got to have basically a private cloud. What are your thoughts on that? >> Yeah, we agree. You can't have a hybrid cloud without that prime element. And you've got to have a strong foundation in terms of how you set up the whole benefit of the cloud model you're building in terms of what you want to try and get back from the cloud. You need a strong foundation. Hyperconversions provides that. We see more and more customers requiring a private cloud, and they're building it with Hyperconversions, in particular HyperFlex. Now to make all that work, they need a good strong cloud operations model to be able to connect both the private and the public. And that's where we look at Intersight. We've got solution around that to be able to connect that around a SaaS offering. That looks around simplified operations, gives them optimization, and also automation to bring both private and public together in that hybrid world. >> Darren let's stay with you for a minute. When you talk to your customers, what are they thinking these days when it comes to implementing hyperconverged infrastructure in both the enterprise and at the edge, what are they trying to achieve? >> So there's many things they're trying to achieve, probably the most brutal honesty is they're trying to save money, that's probably the quickest answer. But, I think they're trying to look in terms of simplicity, how can they remove layers of components they've had before in their infrastructure? We see obviously collapsing of storage into hyperconversions and storage networking. And we've got customers that have saved 80% worth of savings by doing that collapse into a hyperconversion infrastructure away from their Three Tier infrastructure. Also about scalability, they don't know the end game. So they're looking about how they can size for what they know now, and how they can grow that with hyperconvergence very easy. It's one of the major factors and benefits of hyperconversions. They also obviously need performance and consistent performance. They don't want to compromise performance around their virtual machines when they want to run multiple workloads. They need that consistency all all way through. And then probably one of the biggest ones is that around the simplicity model is the management layer, ease of management. To make it easier for their operations, yeah, we've got customers that have told us, they've saved 50% of costs in their operations model on deploying HyperFlex, also around the time savings they make massive time savings which they can reinvest in their infrastructure and their operations teams in being able to innovate and go forward. And then I think probably one of the biggest pieces we've seen as people move away from three tier architecture is the deployment elements. And the ease of deployment gets easy with hyperconverged, especially with Edge. Edge is a major key use case for us. And, what I want, what our customers want to do is get the benefit of a data center at the edge, without A, the big investment. They don't want to compromise in performance, and they want that simplicity in both management and deployment. And, we've seen our analysts recommendations around what their readers are telling them in terms of how management deployment's key for our IT operations teams. And how much they're actually saving by deploying Edge and taking the burden away when they deploy hyperconversions. And as I said, the savings elements is the key bit, and again, not always, but obviously those are case studies around about public cloud being quite expensive at times, over time for the wrong workloads. So by bringing them back, people can make savings. And we again have customers that have made 50% savings over three years compared to their public cloud usage. So, I'd say that's the key things that customers are looking for. Yeah. >> Great, thank you for that Darren. Manish, we have some hard news, you've been working a lot on evolving the HyperFlex line. What's the big news that you've just announced? >> Yeah, thanks Dave. So there are several things that we are announcing today. The first one is a new offer called HyperFlex Express. This is, you know, Cisco Intersight led and Cisco Intersight managed eight HyperFlex configurations. That we feel are the fastest path to hybrid cloud. The second is we are expanding our server portfolio by adding support for HX on AMD Rack, UCS AMD Rack. And the third is a new capability that we are introducing, that we are calling, local containerized witness. And let me take a minute to explain what this is. This is a pretty nifty capability to optimize for Edge environments. So, you know, this leverages the, Cisco's ubiquitous presence of the networking, you know, products that we have in the environments worldwide. So the smallest HyperFlex configuration that we have is a 2-node configuration, which is primarily used in Edge environments. Think of a, you know, a backroom in a departmental store or a oil rig, or it might even be a smaller data center somewhere around the globe. For these 2-node configurations, there is always a need for a third entity that, you know, industry term for that is either a witness or an arbitrator. We had that for HyperFlex as well. And the problem that customers face is, where you host this witness. It cannot be on the cluster because the job of the witness is to, when the infrastructure is going down, it basically breaks, sort of arbitrates which node gets to survive. So it needs to be outside of the cluster. But finding infrastructure to actually host this is a problem, especially in the Edge environments where these are resource constraint environments. So what we've done is we've taken that witness, we've converted it into a container reform factor. And then qualified a very large slew of Cisco networking products that we have, right from ISR, ASR, Nexus, Catalyst, industrial routers, even a Raspberry Pi that can host this witness. Eliminating the need for you to find yet another piece of infrastructure, or doing any, you know, care and feeding of that infrastructure. You can host it on something that already exists in the environment. So those are the three things that we are announcing today. >> So I want to ask you about HyperFlex Express. You know, obviously the whole demand and supply chain is out of whack. Everybody's, you know, global supply chain issues are in the news, everybody's dealing with it. Can you expand on that a little bit more? Can HyperFlex Express help customers respond to some of these issues? >> Yeah indeed Dave. You know the primary motivation for HyperFlex Express was indeed an idea that, you know, one of the folks are on my team had, which was to build a set of HyperFlex configurations that are, you know, would have a shorter lead time. But as we were brainstorming, we were actually able to tag on multiple other things and make sure that, you know, there is in it for, something in it for our customers, for sales, as well as our partners. So for example, you know, for our customers, we've been able to dramatically simplify the configuration and the install for HyperFlex Express. These are still HyperFlex configurations and you would at the end of it, get a HyperFlex cluster. But the part to that cluster is much, much simplified. Second is that we've added in flexibility where you can now deploy these, these are data center configurations, but you can deploy these with or without fabric interconnects, meaning you can deploy with your existing top of rack. We've also, you know, added attractive price point for these, and of course, you know, these will have better lead times because we've made sure that, you know, we are using components that are, that we have clear line of sight from our supply perspective. For partner and sales, this is, represents a high velocity sales motion, a faster turnaround time, and a frictionless sales motion for our distributors. This is actually a set of disty-friendly configurations, which they would find very easy to stalk, and with a quick turnaround time, this would be very attractive for the distys as well. >> It's interesting Manish, I'm looking at some fresh survey data, more than 70% of the customers that were surveyed, this is the ETR survey again, we mentioned 'em at the top. More than 70% said they had difficulty procuring server hardware and networking was also a huge problem. So that's encouraging. What about, Manish, AMD? That's new for HyperFlex. What's that going to give customers that they couldn't get before? >> Yeah Dave, so, you know, in the short time that we've had UCS AMD Rack support, we've had several record making benchmark results that we've published. So it's a powerful platform with a lot of performance in it. And HyperFlex, you know, the differentiator that we've had from day one is that it has the industry leading storage performance. So with this, we are going to get the fastest compute, together with the fastest storage. And this, we are hoping that we'll, it'll basically unlock, you know, a, unprecedented level of performance and efficiency, but also unlock several new workloads that were previously locked out from the hyperconverged experience. >> Yeah, cool. So Darren, can you give us an idea as to how HyperFlex is doing in the field? >> Sure, absolutely. So, both me and Manish been involved right from the start even before it was called HyperFlex, and we've had a great journey. And it's very exciting to see where we are taking, where we've been with the technology. So we have over 5,000 customers worldwide, and we're currently growing faster year over year than the market. The majority of our customers are repeat buyers, which is always a good sign in terms of coming back when they've proved the technology and are comfortable with the technology. They, repeat buyer for expanded capacity, putting more workloads on. They're using different use cases on there. And from an Edge perspective, more numbers of science. So really good endorsement of the technology. We get used across all verticals, all segments, to house mission critical applications, as well as the traditional virtual server infrastructures. And we are the lifeblood of our customers around those, mission critical customers. I think one big example, and I apologize for the worldwide audience, but this resonates with the American audience is, the Super Bowl. So, the SoFi stadium that housed the Super Bowl, actually has Cisco HyperFlex running all the management services, through from the entire stadium for digital signage, 4k video distribution, and it's completely cashless. So, if that were to break during Super Bowl, that would've been a big news article. But it was run perfectly. We, in the design of the solution, we're able to collapse down nearly 200 servers into a few nodes, across a few racks, and have 120 virtual machines running the whole stadium, without missing a heartbeat. And that is mission critical for you to run Super Bowl, and not be on the front of the press afterwards for the wrong reasons, that's a win for us. So we really are, really happy with HyperFlex, where it's going, what it's doing, and some of the use cases we're getting involved in, very, very exciting. >> Hey, come on Darren, it's Super Bowl, NFL, that's international now. And-- >> Thing is, I follow NFL. >> The NFL's, it's invading London, of course, I see the, the picture, the real football over your shoulder. But, last question for Manish. Give us a little roadmap, what's the future hold for HyperFlex? >> Yeah. So, you know, as Darren said, both Darren and I have been involved with HyperFlex since the beginning. But, I think the best is yet to come. There are three main pillars for HyperFlex. One is, Intersight is central to our strategy. It provides a, you know, lot of customer benefit from a single pane of class management. But we are going to take this beyond the lifecycle management, which is for HyperFlex, which is integrated into Intersight today, and element management. We are going to take it beyond that and start delivering customer value on the dimensions of AI Ops, because Intersight really provides us a ideal platform to gather stats from all the clusters across the globe, do AI/ML and do some predictive analysis with that, and return back as, you know, customer valued, actionable insights. So that is one. The second is UCS expand the HyperFlex portfolio, go beyond UCS to third party server platforms, and newer UCS server platforms as well. But the highlight there is one that I'm really, really excited about and think that there is a lot of potential in terms of the number of customers we can help. Is HX on X-Series. X-Series is another thing that we are going to, you know, add, we're announcing a bunch of capabilities on in this particular launch. But HX on X-Series will have that by the end of this calendar year. And that should unlock with the flexibility of X-Series of hosting a multitude of workloads and the simplicity of HyperFlex. We're hoping that would bring a lot of benefits to new workloads that were locked out previously. And then the last thing is HyperFlex data platform. This is the heart of the offering today. And, you'll see the HyperFlex data platform itself it's a distributed architecture, a unique distributed architecture. Primarily where we get our, you know, record baring performance from. You'll see it can foster more scalable, more resilient, and we'll optimize it for you know, containerized workloads, meaning it'll get granular containerized, container granular management capabilities, and optimize for public cloud. So those are some things that we are, the team is busy working on, and we should see that come to fruition. I'm hoping that we'll be back at this forum in maybe before the end of the year, and talking about some of these newer capabilities. >> That's great. Thank you very much for that, okay guys, we got to leave it there. And you know, Manish was talking about the HX on X-Series that's huge, customers are going to love that and it's a great transition 'cause in a moment, I'll be back with Vikas Ratna and Jim Leach, and we're going to dig into X-Series. Some real serious engineering went into this platform, and we're going to explore what it all means. You're watching Simplifying Hybrid Cloud on theCUBE, your leader in enterprise tech coverage. >> The power is here, and here, but also here. And definitely here. Anywhere you need the full force and power of your infrastructure hyperconverged. It's like having thousands of data centers wherever you need them, powering applications anywhere they live, but manage from the cloud. So you can automate everything from here. (upbeat music) Cisco HyperFlex goes anywhere. Cisco, the bridge to possible. (upbeat music) >> Welcome back to theCUBE's special presentation, Simplifying Hybrid Cloud brought to you by Cisco. We're here with Vikas Ratna who's the director of product management for UCS at Cisco and James Leach, who is director of business development at Cisco. Gents, welcome back to theCUBE, good to see you again. >> Hey, thanks for having us. >> Okay, Jim, let's start. We know that when it comes to navigating a transition to hybrid cloud, it's a complicated situation for a lot of customers, and as organizations as they hit the pavement for their hybrid cloud journeys, what are the most common challenges that they face? What are they telling you? How is Cisco, specifically UCS helping them deal with these problems? >> Well, you know, first I think that's a, you know, that's a great question. And you know, customer centric view is the way that we've taken, is kind of the approach we've taken from day one. Right? So I think that if you look at the challenges that we're solving for that our customers are facing, you could break them into just a few kind of broader buckets. The first would definitely be applications, right? That's the, that's where the rubber meets your proverbial road with the customer. And I would say that, you know, what we're seeing is, the challenges customers are facing within applications come from the the way that applications have evolved. So what we're seeing now is more data centric applications for example. Those require that we, you know, are able to move and process large data sets really in real time. And the other aspect of applications I think to give our customers kind of some, you know, pause some challenges, would be around the fact that they're changing so quickly. So the application that exists today or the day that they, you know, make a purchase of infrastructure to be able to support that application, that application is most likely changing so much more rapidly than the infrastructure can keep up with today. So, that creates some challenges around, you know, how do I build the infrastructure? How do I right size it without over provisioning, for example? But also, there's a need for some flexibility around life cycle and planning those purchase cycles based on the life cycle of the different hardware elements. And within the infrastructure, which I think is the second bucket of challenges, we see customers who are being forced to move away from the, like a modular or blade approach, which offers a lot of operational and consolidation benefits, and they have to move to something like a Rack server model for some applications because of these needs that these data centric applications have, and that creates a lot of you know, opportunity for siloing the infrastructure. And those silos in turn create multiple operating models within the, you know, a data center environment that, you know, again, drive a lot of complexity. So that, complexity is definitely the enemy here. And then finally, I think life cycles. We're seeing this democratization of processing if you will, right? So it's no longer just CPU focused, we have GPU, we have FPGA, we have, you know, things that are being done in storage and the fabrics that stitch them together that are all changing rapidly and have very different life cycles. So, when those life cycles don't align for a lot of our customers, they see a challenge in how they can manage this, you know, these different life cycles and still make a purchase without having to make too big of a compromise in one area or another because of the misalignment of life cycles. So, that is a, you know, kind of the other bucket. And then finally, I think management is huge, right? So management, you know, at its core is really right size for our customers and give them the most value when it meets the mark around scale and scope. You know, back in 2009, we weren't meeting that mark in the industry and UCS came about and took management outside the chassis, right? We put it at the top of the rack and that worked great for the scale and scope we needed at that time. However, as things have changed, we're seeing a very new scale and scope needed, right? So we're talking about a hybrid cloud world that has to manage across data centers, across clouds, and, you know, having to stitch things together for some of our customers poses a huge challenge. So there are tools for all of those operational pieces that touch the application, that touch the infrastructure, but they're not the same tool. They tend to be disparate tools that have to be put together. >> Right. >> So our customers, you know, don't really enjoy being in the business of, you know, building their own tools, so that creates a huge challenge. And one where I think that they really crave that full hybrid cloud stack that has that application visibility but also can reach down into the infrastructure. >> Right. You know Jim, I said in my open that you guys, Cisco sort of changed the server game with the original UCS, but the X-Series is the next generation, the generation for the next decade which is really important 'cause you touched on a lot of things, these data intensive workload, alternative processors to sort of meet those needs. The whole cloud operating model and hybrid cloud has really changed. So, how's it going with with the X-Series? You made a big splash last year, what's the reception been in the field? >> Actually, it's been great. You know, we're finding that customers can absolutely relate to our, you know, UCS X-Series story. I think that, you know, the main reason they relate to it is they helped create it, right? It was their feedback and their partnership that gave us really the, those problem areas, those areas that we could solve for the customer that actually add, you know, significant value. So, you know, since we brought UCS to market back in 2009, you know, we had this unique architectural paradigm that we created, and I think that created a product which was the fastest in Cisco history in terms of growth. What we're seeing now is X-Series is actually on a faster trajectory. So we're seeing a tremendous amount of uptake. We're seeing all, you know, both in terms of, you know, the number of customers, but also more importantly, the number of workloads that our customers are using, and the types of workloads are growing, right? So we're growing this modular segment that exist, not just, you know, bringing customers onto a new product, but we're actually bring them into the product in the way that we had envisioned, which is one infrastructure that can run any application and do it seamlessly. So we're really excited to be growing this modular segment. I think the other piece, you know, that, you know, we judge ourselves is, you know, sort of not just within Cisco, but also within the industry. And I think right now is a, you know, a great example, you know, our competitors have taken kind of swings and misses over the past five years at this, at a, you know, kind of the new next architecture. And, we're seeing a tremendous amount of growth even faster than any of our competitors have seen when they announced something that was new to this space. So, I think that the ground up work that we did is really paying off. And I think that what we're also seeing is it's not really a leap frog game, as it may have been in the past. X-Series is out in front today, and, you know, we're extending that lead with some of the new features and capabilities we have. So we're delivering on the story that's already been resonating with customers and, you know, we're pretty excited that we're seeing the results as well. So, as our competitors hit walls, I think we're, you know, we're executing on the plan that we laid out back in June when we launched X-Series to the world. And, you know, as we continue to do that, we're seeing, you know, again, tremendous uptake from our customers. >> So thank you for that Jim. So Vikas, I was just on Twitter just today actually talking about the gravitational pull, you've got the public clouds pulling CXOs one way and you know, on-prem folks pulling the other way and hybrid cloud. So, organizations are struggling with a lot of different systems and architectures and ways to do things. And I said that what they're trying to do is abstract all that complexity away and they need infrastructure to support that. And I think your stated aim is really to try to help with that confusion with the X series, right? I mean, so how so can you explain that? >> Sure. And, that's the right, the context that you built up right there Dave. If you walk into enterprise data center you'll see plethora of compute systems spread all across. Because, every application has its unique needs, and, hence you find drive node, drive-dense system, memory dense system, GPU dense system, core dense system, and variety of form factors, 1U, 2U, 4U, and, every one of them typically come with, you know, variety of adapters and cables and so forth. This creates the siloness of resources. Fabric is (indistinct), the adapter is (indistinct). The power and cooling implication. The Rack, you know, face challenges. And, above all, the multiple management plane that they come up with, which makes it very difficult for IT to have one common center policy, and enforce it all across, across the firmware and software and so forth. And then think about upgrade challenges of the siloness makes it even more complex as these go through the upgrade processes of their own. As a result, we observe quite a few of our customers, you know, really seeing an inter, slowness in that agility, and high burden in the cost of overall ownership. This is where with the X-Series powered by Intersight, we have one simple goal. We want to make sure our customers get out of that complexities. They become more agile, and drive lower TCOs. And we are delivering it by doing three things, three aspects of simplification. First, simplify their whole infrastructure by enabling them to run their entire workload on single infrastructure. An infrastructure which removes the siloness of form factor. An infrastructure which reduces the Rack footprint that is required. An infrastructure where power and cooling budgets are in the lower. Second, we want to simplify by delivering a cloud operating model, where they can and create the policy once across compute network storage and deploy it all across. And third, we want to take away the pain they have by simplifying the process of upgrade and any platform evolution that they're going to go through in the next two, three years. So that's where the focus is on just driving down the simplicity, lowering down their TCOs. >> Oh, that's key, less friction is always a good thing. Now, of course, Vikas we heard from the HyperFlex guys earlier, they had news not to be outdone. You have hard news as well. What innovations are you announcing around X-Series today? >> Absolutely. So we are following up on the exciting X-Series announcement that we made in June last year, Dave. And we are now introducing three innovation on X-Series with the goal of three things. First, expand the supported workload on X-Series. Second, take the performance to new levels. Third, dramatically reduce the complexities in the data center by driving down the number of adapters and cables that are needed. To that end, three new innovations are coming in. First, we are introducing the support for the GPU node using a cableless and very unique X-Fabric architecture. This is the most elegant design to add the GPUs to the compute node in the modular form factor. Thereby, our customers can now power in AI/ML workload, or any workload that need many more number of GPUs. Second, we are bringing in GPUs right onto the compute node, and thereby our customers can now fire up the accelerated VDI workload for example. And third, which is what you know, we are extremely proud about, is we are innovating again by introducing the fifth generation of our very popular unified fabric technology. With the increased bandwidth that it brings in, coupled with the local drive capacity and densities that we have on the compute node, our customers can now fire up the big data workload, the FCI workload, the SDS workload. All these workloads that have historically not lived in the modular form factor, can be run over there and benefit from the architectural benefits that we have. Second, with the announcement of fifth generation fabric, we've become the only vendor to now finally enable 100 gig end to end single port bandwidth, and there are multiple of those that are coming in there. And we are working very closely with our CI partners to deliver the benefit of these performance through our Cisco Validated Design to our CI franchise. And third, the innovations in the fifth gen fabric will again allow our customers to have fewer physical adapters made with ethernet adapter, made with power channel adapters, or made with, the other storage adapters. They've reduced it down and coupled with the reduction in the cable. So very, very excited about these three big announcements that we are making in this month's release. >> Great, a lot there, you guys have been busy, so thank you for that Vikas. So, Jim, you talked a little bit about the momentum that you have, customers are adopting, what problems are they telling you that X-Series addresses, and how do they align with where they want to go in the future? >> That's a great question. I think if you go back to, and think about some of the things that we mentioned before, in terms of the problems that we originally set out to solve, we're seeing a lot of traction. So what Vikas mentioned I think is really important, right? Those pieces that we just announced really enhance that story and really move again, to the, kind of, to the next level of taking advantage of some of these, you know, problem solving for our customers. You know, if you look at, you know, I think Vikas mentioned accelerated VDI. That's a great example. These are where customers, you know, they need to have this dense compute, they need video acceleration, they need tight policy management, right? And they need to be able to deploy these systems anywhere in the world. Well, that's exactly what we're hitting on here with X-Series right now. We're hitting the market in every single way, right? We have the highest compute config density that we can offer across the, you know, the very top end configurations of CPUs, and a lot of room to grow. We have the, you know, the premier cloud based management, you know, hybrid cloud suite in the industry, right? So check there. We have the flexible GPU accelerators that Vikas just talked about that we're announcing both on the system and also adding additional ones to the, through the use of the X-Fabric, which is really, really critical to this launch as well. And, you know, I think finally, the fifth generation of fabric interconnect and virtual interface card, and, intelligent fabric module go hand in hand in creating this 100 gig end to end bandwidth story, that we can move a lot of data. Again, you know, having all this performance is only as good as what we can get in and out of it, right? So giving customers the ability to manage it anywhere, to be able to get the bandwidth that they need, to be able to get the accelerators that are flexible that it fit exactly their needs, this is huge, right? This solves a lot of the problems we can tick off right away. With the infrastructure as I mentioned, X-Fabric is really critical here because it opens a lot of doors here, you know, we're talking about GPUs today, but in the future, there are other elements that we can disaggregate, like the GPUs that solve these life cycle mismanagement issues. They solve issues around the form factor limitations. It solves all these issues for like, it does for GPU we can do that with storage or memory in the future. So that's going to be huge, right? This is disaggregation that actually delivers, right? It's not just a gimmicky bar trick here that we're doing, this is something that customers can really get value out of day one. And then finally, I think the, you know, the future readiness here, you know, we avoid saying future proof because we're kind of embracing the future here. We know that not only are the GPUs going to evolve, the CPUs are going to evolve, the drives, you know, the storage modules are going to evolve. All of these things are changing very rapidly. The fabric that stitches them together is critical, and we know that we're just on the edge of some of the development that are coming with CXL, with some of the PCI Express changes that are coming in the very near future, so we're ready to go. And the X-Fabric is exactly the vehicle that's going to be able to deliver those technologies to our customers, right? Our customers are out there saying that, you know, they want to buy into to something like X-Series that has all the operational benefits, but at the same time, they have to have the comfort in knowing that they're protected against being locked out of some technology that's coming in the future, right? We want our customers to take these disruptive technologies and not be disrupted, but use them to disrupt their competition as well. So, you know, we're really excited about the pieces today, and, I think it goes a long way towards continuing to tell the customer benefit story that X-Series brings, and, you know, again, you know, stay tuned because it's going to keep getting better as we go. >> Yeah, a lot of headroom for scale and the management piece is key there. Just have time for one more question Vikas. Give us some nuggets on the roadmap. What's next for X-Series that we can look forward to? >> Absolutely Dave. As we talked about, and as Jim also hinted, this is a future ready architecture. A lot of focus and innovation that we are going through is about enabling our customers to seamlessly and painlessly adopt very disruptive hardware technologies that are coming up, no refund replace. And, there we are looking into, enabling the customer's journey as they transition from PCI generation four, to five to six without driven replace, as they embrace CXL without driven replace. As they embrace the newer paradigm of computing through the disaggregated memory, disaggregated PCIe or NVMe based dense drives, and so forth. We are also looking forward to X-Fabric next generation, which will allow dynamic assignment of GPUs anywhere within the chassis and much more. So this is again, all about focusing on the innovation that will make the enterprise data center operations a lot more simpler, and drive down the TCO by keeping them not only covered for today, but also for future. So that's where some of the focus is on Dave. >> Okay. Thank you guys we'll leave it there, in a moment, I'll have some closing thoughts. (upbeat music) We're seeing a major evolution, perhaps even a bit of a revolution in the underlying infrastructure necessary to support hybrid work. Look, virtualizing compute and running general purpose workloads is something IT figured out a long time ago. But just when you have it nailed down in the technology business, things change, don't they? You can count on that. The cloud operating model has bled into on-premises locations. And is creating a new vision for the future, which we heard a lot about today. It's a vision that's turning into reality. And it supports much more diverse and data intensive workloads and alternative compute modes. It's one where flexibility is a watch word, enabling change, attacking complexity, and bringing a management capability that allows for a granular management of resources at massive scale. I hope you've enjoyed this special presentation. Remember, all these videos are available on demand at thecube.net. And if you want to learn more, please click on the information link. Thanks for watching Simplifying Hybrid Cloud brought to you by Cisco and theCUBE, your leader in enterprise tech coverage. This is Dave Vellante, be well and we'll see you next time. (upbeat music)

>>Mm. >>Welcome back to the Cube. Special presentation. Simplifying Hybrid Cloud Brought to You by Cisco We're here with Vegas Rattana, who's the director of product management for you? CSS Cisco and James Leach, who was director of business development at Cisco. Gents, welcome back to the Cube. Good to see you again. >>Hey, thanks for having us. >>Okay, Jim, let's start. We know that when it comes to navigating a transition to hybrid cloud, it's a complicated situation for a lot of customers and as organisations that they hit the pavement for their hybrid cloud journeys, one of the most common challenges that they face. What are they telling you? How is Cisco specifically UCS helping them deal with these problems? >>Well, you know, first, I think that's a That's a great question. And, you know, the customer centric view is is the way that we've taken. Um, it's kind of the approach we've taken from Day one, right? So I think that if you look at the challenges that we're solving for their customers are facing, you could break them into just a few kind of broader buckets. The first would definitely be applications, right? That's the That's where the rubber meets your proverbial road. Um, with the customer. And I would say that you know, what we're seeing is the challenges customers are facing within applications come from the way that applications have evolved. So what we're seeing now is more data centric applications. For example, um, those require that we are able to move, um, and process large datasets really in real time. Um, and the other aspect of application, I think, to give our customers kind of some pose some challenges would be around the fact that they're changing so quickly. So the application that exists today or the day that they make a purchase of infrastructure to be able to support that application. That application is most likely changing so much more rapidly than the infrastructure can't keep up with today. So, um, that creates some some challenges around. How do I build the infrastructure? How do I write? Size it without over provisioning, for example. But also there's a need for some flexibility around life cycle and planting those purchase cycles based on the life cycle of the different hardware elements and within the infrastructure, which I think is the second bucket of challenges. We see customers who are being forced to move away from the like a modular or blade approach, which offers a lot of operational and consolidation benefits. And they have to move to something like, um, Iraq server model for some applications because of these needs that these data centric applications have. And that creates a lot of opportunity for silo going. The infrastructure and those silos, in turn, create multiple operating models within the A data centre environment that, you know, again drive a lot of complexity. So that complexity is definitely the the enemy here. Um, and then finally, I think life cycles. We're seeing this democratisation of of processing, if you will, right, so it's no longer just CPU focus. We have GPU. We have F p g A. We have things that are being done in storage and the fabrics that stitch them together that are all changing rapidly and have very different life cycles. So when those life cycles don't align for a lot of our customers, they see a challenge in how they can can manage this these different life cycles and still make a purchase without having to make too big of a compromise in one area or another because of the misalignment of life cycles. So that is a kind of the other bucket. And then finally, I think management is huge, right? So management at its core is really right size for for our customers and give them the most value when it when it meets the mark around scale and scope. Um, back in 2000 and nine, we weren't meeting that mark in the industry and UCS came about and took management outside the chassis, right? We put at the top of the rack, and that works great for the scale and scope we needed at that time. However, as things have changed, we're seeing a very new scale and scope needed, Right? So we're talking about hybrid cloud world that has to manage across data centres across clouds. And, um, you know, having to stitch things together for some of our customers poses a huge challenge. So there are tools for all of those those operational pieces that that touched the application that touched the infrastructure. But they're not the same tool. They tend to be, um, disparate tools that have to be put together. So our customers, you know, don't really enjoy being in the business of building their own tools. So, um, so that creates a huge challenge. And one where I think that they really crave that full hybrid cloud stack that has that application visibility but also can reach down into the infrastructure. >>Right? You know, Jim, I said in my my Open that you guys, Cisco sort of changed the server game with the original UCS. But the X Series is the next generation, the generation of the next decade, which is really important cause you touched on a lot of things. These data intensive workloads, alternative processors to sort of meet those needs. The whole cloud operating model and hybrid cloud has really changed. So how's it going with the X Series? You made a big splash last year. What's the reception been in the field? >>Actually, it's been great. Um, you know, we're finding that customers can absolutely relate to our UCS X series story. Um, I think that the main reason they relate to it as they helped create it, right, it was their feedback and their partnership that they gave us Really, those problem areas, those, uh, those areas that we could solve for the customer that actually add significant value. So, you know, since we brought you see s to market back in 2000 and nine, we had this unique architectural, um uh, paradigm that we created. And I think that created a product which was the fastest in Cisco history. Um, in terms of growth, Um, what we're seeing now is X series is actually on a faster trajectory. So we're seeing a tremendous amount of uptake. We're seeing, uh, both in terms of the number of customers. But also, more importantly, the number of workloads that our customers are using and the types of workloads are growing. Right? So we're growing this modular segment that exists not just, um, you know, bringing customers onto a new product, But we're actually bringing them into the product in the way that we had envisioned, which is one infrastructure that can run any application and do it seamlessly. So we're really excited to be growing this modular segment. Um, I think the other piece, you know that, you know, we judge ourselves is, you know, sort of not just within Cisco, but also within the industry and I think right now is a You know, a great example. Our competitors have taken kind of swings and misses over the past five years at this, um, at a kind of a new next architecture, and we're seeing a tremendous amount of growth even faster than any any of our competitors have seen. When they announced something, um, that was new to this space. So I think that the ground up work that we did is really paying off. Um, and I think that what we're also seeing is it's not really a leapfrog game, Um, as it may have been in the past, Um, X series is out in front today, and we're extending that lead with some of the new features and capabilities we have. So we're delivering on the story that's already been resonating with customers, and we're pretty excited that we're seeing the results as well. So as our competitors hit walls, I think we're you know, we're executing on the plan that we laid out back in June when we launched that series to the world. And, uh, you know, as we as we continue to do that, um, we're seeing, you know, again tremendous uptake from our customers. >>So thank you for that, Jim. So viscous. I was just on Twitter just today, actually talking about the gravitational pull. You've got the public clouds pulling C x o is one way. And you know I'm Prem folks pulling the other way and hybrid cloud So organisations are struggling with a lot of different systems and architectures and and ways to do things. And I said that what they're trying to do is abstract all that complexity away, and they need infrastructure to support that. And I think your stated aim is really to try to help with that with that confusion with the X series. Right? So how so? Can you explain that? >>Sure. And and and that's the right, Uh, the context that you built up right there, Dave, if you walk into Enterprise Data Centre, you see platform of computer systems spread all across because every application has its unique needs. And hence you find Dr Note Driving system memory system, computing system, coordinate system and a variety of farm factors. When you do, you, for you and every one of them typically come with a variety of adapters and cables and so forth Just create silence of resources. Fabric is broad. The actress brought the power and cooling implications the rack, you know, the space challenges and above all, the multiple management plane that they come of it, which makes it very difficult for I t to have one common centre policy and enforce it all across across the firmware and software and so forth and then think about the great challenges of the baroness makes it even more complex as these go through the great references of their own. As a result, we observe quite a few of our customers. Uh, you know, really, uh, seeing Anna slowness in that agility and high burden, uh, in the cost of overall ownership, this is where the X rays powered by inter side. We have one simple goal. We want to make sure our customers get out of that complexities. They become more Asyl and drive lower tco and we are delivering it by doing three things. Three aspects of simplification first simplify their whole infrastructure by enabling them to run their entire workload on single infrastructure and infrastructure, which removes the narrowness of fun factor and infrastructure which reduces direct from footprint that is required infrastructure were power and cooling better served in the Lord. Second, we want to simplify it with by delivering a cloud operating model where they can create the policy ones across compute network stories and deployed all across. And third, we want to take away the pain they have by simplifying the process of upgrade and any platform evolution that they are going to go through the next 23 years. So that's where the focus is on just driving down the simplicity lowering down there. >>That's key. Less friction is is always a good thing now, of course, because we heard from the hyper flex guys earlier, they had news. Not to be outdone, you have hard news as well. What innovations are you announcing around X series today? >>Absolutely. So we are following up on the excited, exciting extras announcement that we made in June last year. Day and we are now introducing three innovation on experience with the bowl of three things First, expand the supported World War and extra days. Second, take the performance to new levels. Third dramatically reduced the complex cities in the data centre by driving down the number of adapters and cables. To that end, three new innovations are coming in. First, we are introducing the support for the GPU note using a cable list and very unique X fabric architecture. This is the most elegant design to add the GPS to the compute note in the model of form factor thereby, our customers can now power in AML workload on any workload that needs many more number of GPS. Second, we are bringing in GPS right onto the computer note and thereby the our customers can now fire up the accelerated video upload, for example, and turf, which is what you know we are extremely proud about, is we are innovating again by introducing the fifth generation of our very popular unified fabric technology with the increased bandwidth that it brings in, coupled with the local drive capacity and density is that we have on the computer note our customers can now fire up the big data workloads the F C I work. Lord, uh, the FDA has worked with all these workloads that have historically not lived in the model of form. Factor can be run over there and benefit from the architectural benefits that we have. Second, with the announcement of fifth generation fabric, we become the only vendor to now finally enable 100 gig and two and single board banned word and the multiple of those that are coming in there. And we are working very closely with our partners to deliver the benefit of these performance through our Cisco validated design to oversee a franchise. And third, the innovations in, uh, in the in the fifth and public again allow our customers to have fewer physical adapters, made the Internet adapter made with our general doctors or maybe the other stories adapters. They reduced it down and coupled with the reduction in the cable so very, very excited about these three big announcements that we're making in this part of the great >>A lot There. You guys have been busy. So thank you for that. Because so, Jim, you talked a little bit about the momentum that you have. Customers are adopting. What problems are they telling you that X series addresses and and how do they align with where where they want to go in the future? >>Um, that's a great question. I think if you go back to um and think about some of the things that we mentioned before. Um, in terms of the problems that we originally set out to solve, we're seeing a lot of traction. So what the cost mentioned, I think, is really important, right? Those pieces that we just announced really enhanced that story and really move again to kind of to the next level of, of taking advantage of some of these problem solving for our customers. You know, if you look, you know, I think the cost mentioned accelerated VD. That's a great example. Um, these are where customers you know, they need to have this dense compute. They need video acceleration, they need type policy management, right. And they need to be able to deploy these, um, these systems anywhere in the world. Well, that's exactly what we're hitting on here with X series right now, we're hitting the mark in every every single way, right? We have the highest compute config density that we can offer across the, you know, the very top end configurations of CPUs. Um, and a lot of room to grow. Um, we have the the premier cloud based management. You know, hybrid cloud suite. Um uh, in the industry. Right. So check there. We have the flexible GPU accelerators that that the cost just talked about that we're announcing both on the system and also adding additional ones to the through the use of the X fabric, which is really, really critical to this launch as well. And, uh, you know, I think finally, the fifth generation of fabric interconnect and virtual interface card, um, and an intelligent fabric module go hand in hand in creating this 100 gig and end bandwidth story that we can move a lot of data again. You know, having all this performance is only as good as what we can get in and out of it, right? So giving customers the ability to manage it anywhere be able to get the bandwidth that they need to be able to get the accelerators that are flexible to that fit exactly their needs. This is huge, right? This solves a lot of the problems we can take off right away with the infrastructure. As I mentioned, X fabric is really critical here because it opens a lot of doors here. We're talking about GPS today, but in the future, there are other elements that we can disaggregate like the GPS that solve these lifecycle mismanagement issues. They solve issues around the form factor limitations. It solves all these issues for like it does for GPU. We can do that with storage or memory in the future, So that's going to be huge, right? This is disaggregate Asian that actually delivers right. It's not just a gimmicky bar trick here that we're doing. This is something that that customers can really get value out of Day one. And then finally, I think the future readiness here. You know, we avoid saying future proof because we're kind of embracing the future here. We know that not only are the GPS going to evolve, the CPUs are going to evolve the drives, the storage modules are going to evolve. All of these things are changing very rapidly. The fabric that stitches them together. It's critical, and we know that we're just on the edge of some of the developments that are coming with C XL with with some of the the PC express changes that are coming in the in the very near future. So we're ready to go X and the X fabric is exactly the vehicle that's going to be able to deliver those technologies to our customers. Our customers are out there saying that you know, they want to buy into something like X Series that has all the operational benefits, but at the same time, they have to have the comfort in knowing that they're protected against being locked out of some technology that's coming in the future. We want our customers to take these disruptive technologies and not be disrupted, but use them to disrupt, um, their competition as well. So, um, you know, we're really excited about the pieces today, and I think it goes a long way towards continuing to tell the customer benefit story that X Series brings And, um, again, stay tuned because it's going to keep getting better as we go. >>A lot of headroom, uh, for scale and the management piece is key. There just have time for one more question because talk to give us some nuggets on the road map. What's next for? For X X series that we can look forward to? >>Absolutely Dave, as as we talked about. And James also hinted this is the future radio architecture, a lot of focus and innovation that we are going through is about enabling our customers to seamlessly and painlessly adopt very disruptive hardware technologies that are coming up no infantry place. And there we are, looking into enabling the customer journey as the transition from PCH in less than 4 to 5 to six without rip and replace as they embraced the Excel without rip and replace as they embrace the newer paradigm of computing through the desegregated memory desegregated P. C, A, r N B and dance drives and so forth. We're also looking forward to extract Brick Next Generation, which will and now that dynamic assignment of GPS anywhere within the chassis and much more. Um, so this this is again all about focusing on the innovation that will make the Enterprise Data Centre operations a lot more simpler and drive down the PCO by keeping them not only covered for today, but also for future. So that's where some of the focus is on there. >>Okay, Thank you guys. We'll leave it there in a moment. I'll have some closing thoughts. >>Mhm

>>mhm. >>With me now are Manish Agarwal, senior director of product management for Hyper Flex at Cisco at Flash for all number four. Love that on Twitter And Deron Williams, the director of business development and sales for Cisco Mister Hyper flex at Mr Hyper Flex on Twitter. Thanks, guys. Hey, we're going to talk about some news and and hyper flex and what role it plays in accelerating the hybrid cloud journey. Gentlemen, welcome to the Cube. Good to see you. >>Thanks, David. >>Thanks. Hi, >>Daryn. Let's start with you. So for hybrid cloud you gotta have on Prem Connection. Right? So you've got to have basically a private cloud. What are your thoughts on that? >>Yeah, we agree. You can't, but you can't have a hybrid cloud without that private element. And you've got to have a strong foundation in terms of how you set up the whole benefit of the cloud model you're building in terms of what you want to try and get back from the cloud, you need a strong foundation. I'm conversions provides that we see more and more customers requiring a private cloud, and they're building with hyper convergence in particular hyper flex no to make all that work. They need a good, strong Cloud operations model to be able to connect both the private and the public. And that's where we look at insight. We've got solution around that. To be able to connect that around a Saas offering that looks around simplified operations, gives them optimisation and also automation to bring both private and public together in that hybrid world. >>Darren, let's stay with you for a minute when you talk to your customers. What are they thinking these days, when it comes to implementing hyper converged infrastructure in both the the enterprise and and at the edge? What are they trying to achieve? >>So there's many things they're trying to achieve? Probably the most brutal honesty is they're trying to save money. That's probably the quickest answer, but I think they're trying to look at in terms of simplicity. How can they remove layers of components they've had before in their infrastructure? We see obviously collapsing of storage into hyper conversions and storage networking, and we've got customers that have saved 80% worth of savings by doing that, a collapse into hyper conversion infrastructure away from their three tier infrastructure. Also about scalability. They don't know the end game, so they're looking about how they can size for what they know now and how they can grow that with hyper conversions. Very easy is one of the major factors and benefits of hyper conversions. They also obviously need performance and consistent performance. They don't want to compromise performance around their virtual machines when they want to run multiple workloads. They need that consistency all the way through. And then probably one of the biggest ones is that around. The simplicity model is the management layer ease of management to make it easier for their operations that we've got customers that have told us they've saved 50% of costs in their operations model, deploying out flex also around the time savings. They make massive time savings which they can reinvest in their infrastructure and their operations teams in being able to innovate and go forward. And then I think that we one of the biggest pieces we've seen as people move away from three tier architecture is the deployment elements, and the ease of deployment gets easy with hyper converged, especially with edge edges of major key use case for us and what I want. What our customers want to do is get the benefit of the data centre at the edge without a big investment. They don't compromise in performance, and they want that simplicity in both management employment. And we've seen analysts recommendations around what their readers are telling them in terms of how management deployments key for it, operations teams and how much they're actually saving by deploying edge and taking the burden away when they deployed hyper conversions. As I said, the savings elements to keep it and again, not always, but obviously those are his studies around about public Cloud being quite expensive at times over time for the wrong workloads. So by bringing them back, people can make savings. We again have customers that have made 50% savings over three years compared to their public cloud usage. So I'd say that's the key things that customers looking for >>Great. Thank you for that, Darrin minutes. We have some hard news. You've been working a lot on evolving the hyper flex line. What's the big news that you've just announced? >>Yeah, Thanks. Leave. So there are several things that we are announcing today. the first one is a new offer, um, called hyper Flex Express. This is, you know, Cisco Inter site lead and Cisco and decide managed it Hyper flex configurations that we feel are the fastest part to hybrid cloud. The second is we're expanding our server portfolio by adding support for HX on AM Iraq, U. C s and Iraq. And the third is a new capability that we're introducing that we're calling local contemporaries witness. And let me take a minute to explain what this is. This is a very nifty capability to optimise for forage environments. So, you know, this leverages the Ciscos ubiquitous presence. Uh, the networking, um, you know, products that we have in the environments worldwide. So the smallest hyper flex configuration that we have is, uh it do not configuration, which is primarily used in edge environment. Think of a, you know, a back home in a department store or a oil rig. Or it might even be a smaller data centre, uh, somewhere, uh, on the globe. For these two not configurations. There is always a need for a third entity that, you know, industry term for that is either a witness or an arbitrator. Uh, we had that for hyper flex as well. The problem that customers faces where you host this witness it cannot be on the cluster because it's the job of the witnesses to when the when the infrastructure is going down, it basically breaks, um, sort of upgrade rates. Which note gets to survive, so it needs to be outside of the cluster. But finding infrastructure, uh, to actually host this is a problem, especially in the edge environments where these are resource constrained environment. So what we've done is we've taken that witness. We've converted it into a container reform factor and then qualified a very large a slew of Cisco networking products that we have right from S. R. S R. Texas catalyst, industrial routers, even even a raspberry pi that can host host this witness, eliminating the need for you to find yet another piece of infrastructure or doing any, um, you know, care and feeding of that infrastructure. You can host it on something that already exists in the environment. So those are the three things that we're announcing today. >>So I want to ask you about hyper Flex Express. You know, obviously the whole demand and supply chain is out of whack. Everybody's global supply chain issues are in the news. Everybody's dealing with it. Can you expand on that? A little bit more Can can hyper flex express help customers respond to some of these issues. >>Yeah, indeed. The, uh, you know, the primary motivation for hyper Flex Express was indeed, uh, an idea that, you know, one of the folks around my team had, which was to build a set of hyper flex configurations that are, you know, would have a shorter lead time. But as we were brainstorming, we were actually able to tag on multiple other things and make sure that, you know, there is in it for something in it for customers, for sales as well as our partners. So, for example, you know, for customers, we've been able to dramatically simplify the configuration and the instal for hyper flex express. These are still hypertext configurations, and you would, at the end of it, get a hyper flex cluster. But the part to that cluster is much much simplifying. Second is that we've added in flexibility where you can now deploy these, uh, these are data centre configurations But you can deploy these with or without fabric interconnects, meaning you can deploy it with your existing top of rack. Um, we've also, you know, already attract attractive price point for these. And of course, you know these will have better lead times because we made sure that, you know, we are using components that are that we have clear line of sight from a supply perspective for partner and sales. This is represents a high velocity sales motion, a faster turnaround time, Uh, and a frictionless sales motion for our distributors. Uh, this is actually a settled, risky, friendly configurations, which they would find very easy to stalk and with a quick turnaround time, this would be very attractive for the deceased as well. >>It's interesting many. So I'm looking at some fresh survey data. More than 70% of the customers that were surveyed this GTR survey again mentioned at the top. More than 70% said they had difficulty procuring, uh, server hardware and networking was also a huge problem. So so that's encouraging. What about Manisha AMG that's new for hyper flex? What's that going to give customers that they couldn't get before? >>Yeah, so you know, in the short time that we've had UCS am direct support, we've had several record breaking benchmark results that we've published. So it's a it's a It's a powerful platform with a lot of performance in it and hyper flex. Uh, you know, the differentiator that we've had from Day one is that it is. It has the industry leading storage performance. So with this, we're going to get the fastest compute together with the fastest storage and this we are hoping that will basically unlock, you know, a unprecedented level of performance and efficiency, but also unlock several new workloads that were previously locked out from the hyper converged experience. >>Yeah, cool. Uh, so, Darren, can >>you can you give us >>an idea as to how hyper flexes is doing in the field? >>Sure, Absolutely So both me and my initial been involved right from the start and before it was called Hyper Flex, and we've had a great journey, and it's very excited to see where we're taking where we've been with the technology. So we have over 5000 customers worldwide, and we're currently growing faster year over year than the market. The majority of our customers are repeat buyers, which is always a good sign in terms of coming back when they approved the technology and are comfortable with technology. They repeat by for expanding capacity, putting more workloads on. They're using different use cases on there. And from an energy perspective, more numbers of science so really good. Endorsement the technology. We get used across all verticals or segments, um, to house mission critical applications as well as the traditional virtual server infrastructures. Uh, and we are the lifeblood of our customers around those mission critical customers think one example, and I apologise for the worldwide audience. But this resonates with the American audiences the Super Bowl. So the sofa like stadium that housed the Super Bowl actually has Cisco hyper Flex running all the management services through from the entire stadium for digital signage. Four K video distribution, and it's complete completely cashless. So if that were to break during Super Bowl, that would have been a big, uh, news article, but it was run perfectly. We in the design of the solution, we're able to collapse down nearly 200 servers into a few notes across a few racks and have 100 120 virtual machines running the whole stadium without missing a heartbeat. And that is mission critical for you to run Super Bowl and not be on the front of the press afterwards for the wrong reasons. That's a win for us. So we really are really happy with High Flex where it's going, what it's doing. And some of the use cases were getting involved in very, very excited. >>Come on, Darren. It's Super Bowl NFL. That's a That's international now. And, you know, the NFL >>NFL. It's >>invading London. Of course I see the picture of the real football over your shoulder, But last question for many is give us a little roadmap. What's the future hold for hyper flex? >>Yeah, so you know, as Darren said, both Darren and I have been involved the type of flicks since the beginning, Uh, but I think the best is yet to come. There are three main pillars for for hyper Flex. One is in. The site is central to our strategy. It provides a lot of customer benefit from a single pane of glass management. But we're going to take this beyond the Lifecycle management, which is for hyper flex, which is integrated in winter side today and element management. We're going to take it beyond that and start delivering customer value on the dimensions of a job. Because Interstate really provides us an ideal platform to gather starts from all the clusters across the globe. Do AML and do some predictive analysis with that and return it back as, uh, you know, customer valued, um, actionable insights. So that is one. The second is you'll see us expand the hyper flex portfolio. Go beyond you see us to third party server platforms, and newer, you see a server platforms as well. But the highlight there is one that I'm really really excited about and think that there is a lot of potential in terms of the number of customers we can help is a checks on X CDs. Experience is another thing that we're able to, uh you know, uh, announcing a bunch of capabilities on in this particular launch. But a check sonic series. We'll have that by the end of this calendar year, and that should unlock with the flexibility of X series of hosting a multitude of workloads and the simplicity of hyper flex. We're hoping that would bring a lot of benefits to new workloads, that we're locked out previously. And then the last thing is hyper flex leader platform. This is the heart of the offering today, Uh, and you'll see the hyper flex data platform itself. It's a distributed architecture, unique distributed architecture primarily where we get our, you know, record breaking performance from you'll see it get faster, more scalable, more resilient. And we'll optimise it for, you know, containerised workloads, meaning it will get granular containerised container granular management capabilities and optimised for public. So those are some things that were the team is busy working on, and we should see that come to fruition. I'm hoping that we'll be back at this forum and maybe before the end of the year and talking about some of these new capabilities. >>That's great. Thank you very much for that. Okay, guys, we got to leave it there and you know many She was talking about the HX on X Series. That's huge. Customers are gonna love that, and it's a great transition because in a moment I'll be back with Vikas Ratna and Jim Leach and we're gonna dig into X series. Some real serious engineering went into this platform, and we're gonna explore what it all means. You're watching simplifying hybrid cloud on the cube, your leader in enterprise tech coverage.

>>Okay, let's start things off Didi Dasgupta is back on the cube to talk about how we're going to simplify hybrid cloud complexity. Didi. Welcome. Good to see you again. >>Hey Dave, thanks for having me. Good to see you again. >>Yeah, our pleasure here. Look, let's start with big picture. Talk about the trends you're seeing from your customers. >>Well, I think first off every customer, these days is a public cloud customer. They do have their on-premise data centers, but every customer is looking to move workloads, use services, cloud native services from the public cloud. I think that's, that's one of the big things that we're seeing while that is happening. We're also seeing a pretty dramatic evolution off the application landscape itself. You've got bare metal applications. You always have virtualized applications and then most modern applications are, are containerized and, you know, managed by Kubernetes. So I think we're seeing a big change in, in the application landscape as well, and probably, you know, triggered by the first two things that I mentioned, the execution venue of the applications, and then the applications themselves it's triggering the change in the it organizations in the development organizations and sort of not only how they work within their organizations, but how they work across all of these different organizations. So I think those are some of the big things that, that I hear about when I talk to customers. >>Well, so it's interesting. I often say Cisco kind of changed the game and in server and compute when it, when it developed the original UCS and you remember there were organizational considerations back then bringing together the server team and the networking team. And of course the, the storage team of, and now you mentioned Kubernetes, that is a total game changer with regard to whole the application development process. So you have to think about a new strategy in that regard. So how have you evolved your strategy? What is your strategy to help customers simplify, accelerate their hybrid cloud journey in that context? >>No, I think you're right back of the origins of UCS. I mean, we, you know, why the networking company builder server, well, we just enabled with the best networking technology. So do compute that and now doing something similar on the software, actually the managing software for our hyperconvergence, for our. And you know, we've been on this journey for about four years, but the software is called intersite. And, you know, we started out with intersite being just the element manager, the management software for Cisco's compute and hyperconverged devices, but then we've evolved it the last few years because we believe that the customer shouldn't have to manage a separate piece of software would do manage the hardware of the underlying hardware and then a separate tool to connect it to a public cloud. And then the third tool to do optimization, workload optimization or performance optimization or cost optimization, a fourth tool do now manage, you know, Kubernetes and like, not just in one, one cluster, one cloud, but multi cluster multicloud. >>They should not have to have a fifth tool that does goes into observability. Anyway, I can go on and on, but you get the idea. We wanted to bring everything onto that same platform that managed their infrastructure, but it's also the platform that enables the simplicity of hybrid cloud operations, automation. It's the same platform on which you can use to manage the Kubernetes infrastructure, Kubernetes clusters. I mean, whether it's on-prem or in the cloud. So overall that's the strategy, bring it to a single platform and a platform is a loaded word, but we'll get into that a little bit, you know, in this, in this conversation, but that's the overall strategy simplify? >>Well, you know, he brought a platform. I, I like to say platform beats products, but you know, there was a day and you could still point to some examples today in the it industry where, Hey, another tool we can monetize that and another one to solve a different problem. We can monetize that. And so tell me more about how intersite came about. You obviously sat back, you saw what your customers were going through. You said we can do better. So tell us the story there. >>Yeah, absolutely. So look, it started with, you know, three or four guys getting in a room and saying, look, we've had this, you know, management software, UCS manager, UCS director, and these are just the Cisco's management, you know, for our softwares, for our own platform. Then every company has their, their own flavor. We said, we, we took on this bold goal of like, we're not when we rewrite this or we improve on this, we're not going to just write another piece of software. We're going to create a cloud service, or we're going to create a SAS offering because the same in the infrastructure built by us, whether it's on networking or compute or the cyber talk software, how do our customers use it? Well, they use it to write and run their applications, their SAS services, every customer, every customer, every company today is a software company. >>They live and die by how their assets work or don't. And so we were like, we want to eat our own dog food here, right? We want to deliver this as a SAS offering. And so that's how it started being on this journey for about four years, tens of thousands of customers. But it, it was pretty big boat invasion. Cause you know, the big change with SAS is your, as you're familiar, Dave is the job of now managing this, this piece of software is not on the customer, it's on the vendor, right? This can never go down. We have a release every Thursday, new capabilities. And we've learned so much along the way, whether it's around scalability, reliability, working with our own company's security organizations on what can or cannot be in a SAS service. So again, it's just been a wonderful journey, but I wanted to point out that we are in some ways eating our own dog food. Cause we built a SAS application that helps other companies deliver their SAS applications. >>So Cisco, I look at Cisco's business model and I, I of course compare it to other companies in the infrastructure business and obviously a very profitable company or large company you're growing faster than, than, than most of the traditional competitors. And so that means that you have more to invest. You, you, you can, you can afford things like stock buybacks, and you can invest in R and D. You don't have to make those hard trade-offs that a lot of your competitors have to make. So It's never enough, right? Never enough. But, but, but in speaking of R and D and innovations that you're introducing, I'm specifically interested in, how are you dealing with innovations to help simplify hybrid cloud in the operations there and prove flexibility and things around cloud native initiatives as well? >>Absolutely. Absolutely. Well, look, I think one of the fundamentals where we're philosophically different from a lot of options that I see in the industry is we don't need to build everything ourselves. We don't, I just need to create a damn good platform with really good platform services, whether it's, you know, around search ability, whether it's around logging, whether it's around, you know, access control multi-tenants I need to create a really good platform and make it open. I do not need to go on a shopping spree to buy 17 and a half companies and then figure out how to stitch it all together because it's, it's almost impossible if it's impossible for us as a vendor, it's, it's three times more difficult, but for the customer who then has to consume it. So that was the philosophical difference in how we went about building in our sites. >>We've created a harden platform that's that's always on. Okay. And then you, then the magic starts happening. Then you get partners, whether it is, you know, infrastructure partners, like, you know, some of our storage partners like NetApp or your, or, you know, others who want to their conversion infrastructure is also to be managed or are there other SAS offerings, software vendors who have now become partners? Like we did not, we did not write Terraform, you know, but we partnered with Tashi and now, you know, Terraform services available on the intercept platform. We did not write all the algorithms for workload optimization between a public cloud and on-prem we partnered with a company called urbanomics. And so that's now an offering on the intercept platform. So that's where we're philosophically different and sort of, you know, w how we have gone about this. And it actually ducked a dovetails well into some of the new things that I want to talk about today, that we're announcing on the underside platform, where we're actually been announcing the ability to attach and, and be able to manage Kubernetes clusters, which are not on prem. They're actually on AWS, on Azure, soon coming on, on GC, on, on GKE as well. So it really doesn't matter. We're not telling a customer if you're comfortable building your applications and running Kubernetes clusters on, you know, in AWS or Azure, stay there, but in terms of monitoring, managing it, you can use in our site, since you're using it on prem, you can use that same piece of software to manage Kubernetes clusters in a public cloud, or even manage VMs in, in a, in an instance. >>So the fact that you could, you mentioned storage, pure net app. So it's intersite can manage that infrastructure. I remember the hot-seat deal. It caught my attention. And of course, a lot of companies want to partner with Cisco because you've got such a strong ecosystem, but I thought that was an interesting move Turbonomic. You mentioned. And now you're saying Kubernetes in the public cloud, so a lot different than it was 10 years ago. So my last question is, how do you see this hybrid cloud evolving? I mean, you had private cloud and you had public cloud, and it was kind of a tug of war there. We see these, these, these two worlds coming together. How will that evolve over the next few years? >>Well, I think it's, it's the evolution of the model and really look at know $2 or $3 depending on, you know, how you're keeping time. But I think one thing is become very clear. Again, we may be eating our own dog food. I mean, innercise is a hybrid cloud SAS applications that we've learned. Some of these lessons ourselves. One thing is referred that customers are looking for a consistent model, whether it's on the edge, on the polo public cloud, on-prem no data center doesn't matter. They're looking for a consistent model for operations, for governings or upgrades or liability. They're looking for a consistent operating model. What Mike is the law doesn't mean? I think there's going to be the rise of more custom plugs. It's still going to be hybrid. So obligations will want to reside wherever it makes most sense for them, which is data moving data is it's the most expensive thing. >>So it's going to be co-located with the data that's on the edge, on the edge colo public cloud doesn't matter, but you're basically going to see more customer droughts, more industry-specific clouds. You know, whether it's for finance or constipation or retail industry specific. I think sovereign is going to play a huge role, you know, today, if you look at the cloud providers, you know, American and Chinese companies that these, the rest of the world, when it comes to making good digital citizens, they're they're people and, you know, control. And the distributor cloud is also on edge is, is gonna be the next frontier. And so that's where we are trying to line up our strategy. And if I had to sum it up in one sentence, it's really your cloud, your way. Every customer is on a different journey that will have their choice of workloads, data, you know, uptime, reliability, concerns. That's really what, what we are returning any of our customers. >>You know, I think I agree with you that custom clouds. And I think what you're seeing is you said every company is a software company. Every company is also becoming a cloud company. They're building their own abstraction layers. They're connecting their on-prem to their, to their public cloud. They're doing that. They're, they're doing that across clouds. And they're looking for companies like Cisco to do the hard work. It give me an infrastructure layer that I can build value on top of, because I'm going to take my financial services business to my cloud model or my healthcare business. I don't want to mess around with it. I'm not going to develop, you know, custom infrastructure like an Amazon does. I'm going to look to Cisco in your R and D to do that. Do you buy that? >>Absolutely. I think, again, it goes back to what I was talking about with blacks. You got to get the world a solid open, flexible, and flexible in terms of the technology, flexible in how they want to consume it. Some customers are fine with a SAS software, but as I talk to, you know, my friends in the federal team, no, that does not work. So how they want to consume it. They want to, you know, a hundred percent, no sovereignty. We, we talked about. So, you know, job for a decent structure vendor like ourselves is to give the world an open platform, give them the knobs, give them the right API. But the last thing I will mention is, you know, there's still a place for innovation in hardware. Some of my colleagues are gonna engage me to some of those, you know, details, whether it's on our X series platform or HyperFlex, but it's really, it's going to, it's going to be software defined to SAS service and then, you know, give the world and open rock-solid platform, >>Got to run on something. All right. Thanks, Deedee. Always a pleasure to have you in the cube. Great to see you. >>You're >>Welcome. In a moment, I'll be back to dig into hyperconverged and where fits and how it may even help with addressing some of the supply chain challenges that we're seeing in the market today.

>> From theCUBE Studios in Palo Alto and Boston, bringing you data-driven insights from theCUBE in ETR. This is "Breaking Analysis" with Dave Vellante. >> Cisco is a company at the crossroads. It's transitioning from a high margin hardware business to a software subscription-based model, which also should be high margin through both organic moves and targeted acquisitions. It's doing so in the context of massive macro shifts to digital in the cloud. We believe Cisco's dominant position in networking combined with a large market opportunity and a strong track record of earning customer trust, put the company in a good position to capitalize on cloud momentum. However, there are clear challenges ahead for Cisco, not the least of which is the growing complexity of its portfolio, a large legacy business, and the mandate to maintain its higher profitability profile as it transitions into a new business model. Hello and welcome to this week's Wiki-bond cube insights powered by ETR. In this breaking analysis, we welcome in Zeus Kerravala, who's the founder and principal analyst at ZK Research, long time Cisco watcher who together with me crafted the premise of today's session. Zeus, great to see you welcome to the program. >> Thanks Dave. It's always a pleasure to be with you guys. >> Okay, here's what we're going to talk about today, set the agenda. The catalyst for this session, Zeus and I attended Cisco's financial analyst day. We received a day and a half of firehose presentations, drill downs, interactions, Q and A with Cisco execs and one key customer. So we're going to share our takeaways from these sessions and add our additional thoughts. Now, in particular, we're going to talk about Cisco's TAM, its transformation to a subscription-based model, and how we see that evolving. As always, we're going to bring in some ETR spending data for context and get Zeus' take on what that tells us. And we'll end with a summary of Cisco's cloud strategy and outlook for how it could win in the cloud. So let's talk about Cisco's sort of structure and TAM opportunities. First, Zeus, Cisco has four main lines of business where it's organized it's executives around sort of four product areas. And it's got a large service component as well. Network equipment, SP routing, data center, collaboration that security, and as I say services, that's not necessarily how it's going to market, but that's kind of the way it organizes its ELT, its executive leadership team. >> Yeah, the in fact, the ELT has been organized around those products, as you said. It used to report to the street three product segments, infrastructure platforms, which was by far the biggest, it was all their networking equipment, then applications, and then security. Now it's moved to five new segments, secure agile networks, hybrid work, end to end security, internet for the future and optimized app experiences. And I think what Cisco's trying to do is align their, the way they report along the lines of the way customers buy. 'Cause I think before, you know, they had a very simplistic model before. It was just infrastructure, apps, and security. The ELT is organized around product roadmap and the product innovation, but that's not necessarily the way customers purchase things and so, purchase things so I think they've tried to change things a little bit there. When you look at those segments though, you know, by, it's interesting. They're all big, right? So, by far the biggest distilled networking, which is almost a hundred billion dollar TAM as they reported and they have it growing a about a 9% CAGR as reported by other analyst firms. And when you think about how mature networking is Dave, the fact that that's still growing at high single digit CAGR is still pretty remarkable. So I think that's one of those things that, you know, watchers of Cisco historically have been calling for the network to be commoditized for decades. For as long as I've been watching Cisco, we've been, people have been waiting for the network to be commoditized. My thesis has always been, if you can drive enough innovation into things, you can stave off commoditization and that's what they've done. But that's really the anchor for them to sell all their other products, some of which are higher margin, some which are a little bit sore, but they're all good high margin businesses to your point. >> Awesome. We're going to dig into that. So, so they flattened the organization when Geckler left. You've got Todd Nightingale, Jonathan Davidson, Liz Centoni, and Jeetu Patel who we heard from and we'll make some comments on what we heard from them. One of the big takeaways at the financial analysts meeting was on the TAM, as you just mentioned. Liz Centoni who also is heavily involved in strategy and the CFO Scott Herren, showed this slide, which speaks to the company's TAM and the organizational structure that you were just talking about. So the big message was that Cisco has got a large and growing market, you know, no shortage of available market. Somewhere between eight and 900 billion, depending on which of the slides you pull out of the deck. And ironically Zeus, when you look at the current markets number here on the right hand side of this slide, 260 billion, it just about matches the company's market cap. Maybe an interesting coincidence, but at any rate, what was your takeaway from this data? >> Well, I think, you know, the big takeaway from the data is there's still a lot of room ahead for Cisco to grow, right? Again, this is a, it's a company that I think most people would put in the camp of legacy IT vendor, just because of how long they've been around. But they have done a very good job of staving off innovation. And part of that is just these markets that they play in continue to grow and they continue to have challenges that they can solve. I think one of the things Cisco has done though, since the arrival of Chuck Robbins, is they don't fight these trends anymore, Dave. I know prior to Chuck's arrival, they really fought the tide of software defined networking and you know, trends like that, and even cloud to some extent. And I remember one of the first meetings I had with Chuck, I asked him about that and he said that Cisco will never do that again. That under his watch, if customers are going through a market transition, Cisco wants to lead them through it, not try and hold them back. And I think for that reason, they're able to look at, all of those trends and try and take a leadership position in them, even though you might look at some of those and feel that some of them might be detrimental to Cisco's business in the short term. So something like software defined WANs, which you would throw into secure agile networks, certainly doesn't, may not carry the same kind of RPOs and margins with it that their traditional routers did, but ultimately customers are going to buy it and Cisco would like to be the ones to sell it to them. >> You know, you bring up a great point. This industry is littered, there's a graveyard of executives who fought the trend. Many people, some people remember Ken Olson of Digital Equipment Corporation. "Unix is snake oil," is what he said. IBM mainframe guys said, "PCs are a toy." And of course the history, they were the wrong side of history. The other big takeaway was the shift to software in subscription. They really made a big point of this. Here's a chart Cisco showed a couple of times to make the point that it's one of the largest software companies in the world. You know, in the top 10. They also made the point that Chuck Robbins, when he joined in 2015, and since that time, it's nearly 4x'ed it's subscription software revenue, and roughly doubled its software sales. And it now has an RPO, remaining performance obligations, that exceeds 30 billion. And it's committing to grow its subscription business in the forward-looking statements by 15 to 17% CAGR through 25, which would imply about a doubling of these, the blue lines. Zeus, it's unclear if that forward-looking forecast is just software. I presume it includes some services, but as Herren pointed out, over time, these services will be bundled into the product revenue, same way SAS companies do it. But the point is Cisco is committed, like many of their peers, to moving to an ARR model. But please, share your thoughts on Cisco's move to software subscriptions and how you see the future of consumption-based pricing. >> Yeah, this has been a big shift for Cisco, obviously. It's one that's highly disruptive. It's one that I know gave their partners a lot of angst for a long time because when you sell things upfront, you get a big check for selling that, right? And when you sell things in a subscription model, you get a much smaller check for a number of months over the period of the contract. It also changes the way you deal with the customer. When you sell a one-time product, you basically wipe your hands. You come back in three or four years and say, "it's time to upgrade." When you sell a subscription, now, the one thing that I've tried to talk to Cisco and its partners about is customers don't renew things they don't use. And so it becomes incumbent on the partner, it becomes incumbent upon Cisco to make sure that things that the customer is subscribing to, that they do use. And so Cisco's had to create a customer success organization. They've had to help their partners create those customer success organizations. So it's really changed the model. And Cisco not only made the shift, they've done it faster than they actually had originally forecast. So during the financial analyst day, they actually touted their execution on software, noting that it hit it's 30% revenue as percent of total target well before it was supposed to, it's actually exceeded its targets. And now it's looking to increase that to, it actually raised its guidance in this area a little bit by a few percentage points, looking out over the next few years. And so it's moved to the subscription model, Dave, the thing that you brought up, which I do see as somewhat of a challenge is the shift to consumption-based pricing. So subscription is one thing in that I write you a check every month for the same amount. When I go to the consumption-based pricing, that's easy to do for cloud services, things like WebEx or Duo or, you know, CloudLock, some of the security products. That that shift should be relatively simple. If customers want to buy it that way. It's unclear as to how you do that when you're selling on-prem equipment with the software add-on to it because in that case, you have to put metering technology in to understand how much they're using. You have to have a minimum baseline to start with. They've done it in some respects. The old HCS product that they sold, the Telcos, actually was sold with a minimum commit and then they tacked on a utilization on top of that. So maybe they move into that kind of model. But I know it's something that they've, they get asked about a lot. I know they're still thinking about it, but it's something that I believe is coming and it's going to come pretty fast. >> I want to pick up on that because I think, you know, they made the point that we're one of the top 10 software companies in the world. It's very difficult for hardware companies to make the transition to software. You know, HP couldn't do it. >> Well, no one's done it. >> Well, IBM has kind of done it, but they really struggle. It's kind of this mishmash of tooling and software products that aren't really well-integrated. But, I would say this, everybody now, Cisco, Dell, HPE with GreenLake, Lenovo, pretty much all the traditional hardware players are trying to move to an as a service model or at least for a portion of their business. HPE's all in, Dell transitioning. And for the most part, I would make the following observation. And I'd love to get your thoughts on this. They're pretty much following a SAS like model, which in my view is outdated and kind of flawed from a customer standpoint. All these guys say, "Hey, we're doing this because "this is what the customers want." I think the cloud is really a true consumption based model. And if you look at modern SAS companies, a lot of the startups, they're moving to a consumption based model. You see that with Snowflake, you see that with Stripe. Now they will offer incentives. But most of the traditional enterprise players, they're saying, "Okay, pay us upfront, "commit to some base level. "If you go over it, you know, "we'll charge you for it. "If you go under it, you're still going to pay "for that base level." So it's not true consumption base. It's not really necessarily the customer's best interest. So that's, I think there's some learnings there that are going to have to play out. >> Yeah, the reason customers are shying away from that SAS type model, I think during the pandemic, the one thing we learned, Dave, is that the business will ebb and flow greatly from month to month sometimes. And I was talking with somebody that worked for one of the big hotel chains, and she was telling me that what their CRM providers, she wouldn't tell me who it was, except said it rhymed with Shmalesforce, that their utilization of it went from, you know, from a nice steady level to spiking really high when customers started calling in to cancel hotel rooms. And then it dropped down to almost nothing as we went through that period of stay at home. And now it's risen back up. And so for her, she wanted to move to a consumption-based model because what happens otherwise is you wind up buying for peak utilization, your software subscriptions go largely underutilized the majority of the year, and you wind up paying, you know, a lot more than you need to. If you go to more of a true consumption model, it's harder to model out from a financial perspective 'cause there's a lot of ebbs and flows in the business, but over a longer period of time, it's more cost-effective, right? And so the, again, what the pandemic taught us was we don't really know what we're going to need from a consumption standpoint, you know, nevermind a year from now, maybe even six months from now. And consumption just creates a lot more flexibility and agility. You can scale up, you can scale down. You can bring in users, you can take out users, you can add consultants, things like that. And it just, it's much more aligned with the way businesses are run today. >> Yeah, churn is a silent killer of a software company. And so there's retention is the key here. So again, I think there's lots of learning. Let's put Cisco into context with some of its peers. So this chart we developed compares five companies to Cisco. Core Dell, meaning Dell, without VMware. VMware, HPE, IBM, we've put an AWS, and then Cisco as, IBM, AWS and Cisco is the integrated plays. So the chart shows the latest quarterly revenue multiplied by four to get a run rate, a three-year growth outlook, gross margin percentage, market cap, and revenue multiple. And the key points here are that one, Cisco has got a pretty awesome business model. It's got 60% gross margin, strong operating margins, not shown here, but in the mid twenties, 25%. It's got a higher growth rate than most of its peers. And as such, a much better, multiple than say, for instance, Core Dell gets 33 cents on the revenue dollar. HPE is double that. IBM's below two X. Cisco's revenue multiple rivals VMware, which is a pure software company. Now in a large part that's because VMware stock took a hit recently, but still the point is obvious. Cisco's got a great business. Now for context, we've added AWS, which blows away any company on this chart. We've inferred a market cap of nearly 600 billion, which frankly is conservative at a 10 X revenue multiple given it's inferred margins and growth rate. Now Zeus, if AWS were a separate company, it could have a market cap that approached 800 billion in my view. But what does this data tell you? >> Well, it just tells me that Cisco continues to be a very well-run company that has staved off commoditization, despite the calling for it for years. And I think the big lesson, and I've talked to financial analysts about this over the years, is that if, I don't really believe anything in this world is a commodity, Dave. I think even when Cisco went to the server market, if you remember back then, they created a new way of handling memory management. They were getting well above average margins for service, albeit less than Cisco's network margins, but still above average for server margins. And so I think if you can continue to innovate, you will see the margin stay where they are. You will see customers continue to buy and refresh. And I think one of the challenges Cisco's had in the past, and this is where the subscription business will help, is getting customers to stay with the latest and greatest. Prior to this refresh of network equipment, some of the stuff that I've seen in the fields, 10, 15 years old, once you move to that sell me a box and then tack on the subscription revenue that you pay month by month, you do drive more consistent refresh. Think about the way you just handle your own mobile phone. If you had to go pay, you know, a thousand dollars every three years, you might not do it at that three-year cycle. If you pay 40 bucks a month, every time there's a new phone, you're going to take it, right? So I think Cisco is able to drive greater, better refresh, keep their customers current, keep the features in there. And we've seen that with a lot of the new products. The new Cat 9,000, some of the new service provider products, the new wifi products, they've all done very well. In fact, they've all outpaced their previous generation products as far as growth rate goes. And so I think that is a testament to the way they've run the business. But I do think when people bucket Cisco in with HP and Dell, and I understand why they do, their businesses were similar at one time, it's really not a true comparison anymore. I think Cisco has completely changed their business and they're not trying to commoditize markets, they're trying to drive innovation and keep the margins up, where I think HP and Dell tend to really compete on price versus innovation. >> Well, and we are going to get to this point about the tailwinds and headwinds and cloud, and how Cisco to do it. But, to your point about, you know, the cell phone analogy. To the extent that Cisco can make that seamless for customers could hide that underlying complexity, that's going to be critical for the cloud. Now, but before we get there, I want to talk about one of the reasons why Cisco such a high multiple, and has been able to preserve its margins, to your point, not being commoditized. And it's been able to grow both organically, but also has a strong history of M and A. It's this chart shows a dominant position in core networking. So this shows, so ETR data within the Fortune 500. It plots companies in the ETR taxonomy in two dimensions, net score on the vertical axis, which is a measure of spending velocity, and market share on the horizontal axis, which is a measure of presence in the survey. It's not like IDC market share, it's mentioned market share if you will. The point is Cisco is far and away the most pervasive player in the market, it's generally held its dominant position. Although, it's been under pressure in the last few years in core networking, but it retains or maintains a very respectable net score and consistently performs well for such a large company. Zeus, anything you'd add with respect to Cisco's core networking business? >> Yeah, it's maintained a dominant network position historically. I think part of because it drives good products, but also because the competitive landscape, historically has been pretty weak, right? We saw companies like 3Com and Nortel who aren't around anymore. It'll be interesting to see moving forward now that companies like VMware are involved in networking. AWS is interested in networking. Arista is a much stronger company. You know, Juniper bought Mist and is in better position. Even Extreme Networks who most people thought was dead a few years ago has made a number of acquisitions and is now a billion dollar company. So while Cisco has done a great job of execution, they've done a great job on the innovation side, their competitive landscape, looking out over the next five years, I think is going to be more difficult than it has been over the previous five years. And largely, Dave, I think that's good for Cisco. I think whenever Cisco's pressed a little bit from competition, they tend to step on the innovation gas a little bit more. And I look back and even just the transition when VMware bought Nicira, that got Cisco's SDN business into gear, like nothing else could have, right? So competition for that company, they always seem to respond well to it. >> So, let's break down Cisco's net score a little bit. Explain why the company has been able to hold its spending momentum despite its large size. This will give you a little insight to the survey. So this chart shows the granular components of net score. The lime green is new adoptions to Cisco. The forest green is spending more than 6%. The gray is flat plus or minus 5%. The pink is spending drops by more than 5%. And the red is we're chucking the platform, we're getting off. And Cisco's overall net score here is 25%, which for a company of its size speaks to the relationships that it has with customers. It's of course got a fat middle in the gray area, like all sort of large established companies. But very low defections as well, it's got low new adoptions. But very respectable. So that is background, Zeus. Let's look at spending momentum over time across Cisco's portfolio. So this chart shows Cisco's net score by that methodology within the ETR taxonomy for Cisco over three survey periods. And what jumps out is Meraki on the left, very strong. Virtualization business, its core networking, analytics and security, all showing upward momentum. AppD is a little bit concerning, but that could be related to Cisco's sort of pivot to full stack observability. So maybe AppD is being bundled there. Although some practitioners have cited to us some concerns in that space. And then WebEx at the end of the chart, it's showing some relative strength, but not that high. Zeus, maybe you could comment on Meraki and any other takeaways across the portfolio. >> Yeah, Meraki has proven to be an excellent acquisition for Cisco. In fact, you might, I think it's arguable to say it's its best acquisition in history going all the way back to camp Kalpana and Grand Junction, the ones that brought up catalyst switches. So, in fact, I think Meraki's revenue might be larger than security now. So, that shows you the momentum it has. I think one of the lessons it brought to Cisco was that simpler is better, sometimes. I think when they first bought Meraki, the way Meraki's deployed, it's very easy to set up. There's a lot of engineering work though that goes into making a product simple to use. And I think a lot of Cisco engineers historically looked at Meraki as, that's a little bit of a toy. It's meant for small businesses, things like that, but it's not for enterprise. But, Rocky's done a nice job of expanding the portfolio, of leveraging the cloud for analytics and showing you a lot of things that you wouldn't necessarily get from traditional networking equipment. And one of the things that I was really delighted to see was when they put Todd Nightingale in charge of all the networking business, because that showed to me that Chuck Robbins understood that the things Meraki were doing were right and they infuse a little bit of Meraki into the rest of the company. You know, that's certainly a good thing. The other areas that you showed on the chart, not really a surprise, Dave. When you think of the shift hybrid work and you think of the, some of the other transitions going on, I think you would expect to see the server business in decline, the storage business, you know, maybe in a little bit of decline, just because people aren't building out data centers. Where the other ones are related more to hybrid working, hybrid cloud, things like that. So it is what you would expect. The WebEx one was interesting too, because it did show somewhat of a dip and then a rise. And I think that's indicative of what we've seen in the collaboration space since the pandemic came about. Companies like Zoom and RingCentral really got a lot of the headlines. Again, when you, the comment I made on competition, Cisco got caught a little bit flat-footed, they've caught up in features and now they really stepped on the gas there. Chuck joked that he gave the WebEx team a bit of a blank check to go do what it had to do. And I don't think that was a joke. I think he actually did that because they've added more features into WebEx in the last year then I think they did the previous five years before that. >> Well, let's just drill into video conferencing real quick here, if we could. Here's that two dimensional view, again, showing net score against market share or pervasiveness of mentions, and you can see Microsoft Teams in the upper right. I mean, it's off the chart, literally. Zoom's well ahead of Cisco in terms of, you know, mentions presence. And that could be a spate of freemium, you know, but it's basically a three horse race in this game. And Cisco, I don't think is trying to take Zoom head on, rather it seems to be making WebEx a core part of its broader collaboration agenda. But Zeus, maybe you could comment. >> Well, it's all coming together, right? So, it's hard to decouple calling from video from meetings. All of the vendors, including Teams, are going after the hybrid work experience. And if you believe the future is hybrid and not just work from home, then Cisco does have a pretty interesting advantage because it's the only one that makes its own end points, where Teams and Zoom doesn't. And so that end to end experience it can deliver. The Microsoft Teams one's interesting because that product, frankly, when you talk to users, it doesn't have a great user score, like as far as user satisfaction goes, but the one thing Microsoft has done a very good job of is bundling it in to the Office365 licenses, making it very easy for IT to deploy. Zoom is a little bit in the middle where they've appealed to the users. They've done a better job of appealing to IT, but there is a, there is a battleground now going on where video's not just video. It includes calling, includes meetings, includes room systems now, and I think this hybrid work friend is going to change the way we think about these meeting tools. >> Now we'd be remiss if we didn't spend a moment talking about security as a key part of Cisco's business. And we have a graphic on this same kind of X, Y. And it's been, we've seen several quarters of growth. Although, the last quarter security growth was in the low single digits, but Cisco is a major player in security. And this X, Y graph shows, they've got both a large presence and a solid spending momentum. Not nearly as much momentum as Okta or Zscaler or a CrowdStrike and some of the smaller companies, but they're, these guys are on a rocket ship, but others that we featured in these episodes, but much more than respectable for Cisco. And security is critical to the strategy. It's a big part of the subscriber base. And the last thing, Zeus, I'll say about Cisco made the point in analyst day, that this market is crowded. You can see that in this chart. And their goal is to simplify this picture and make it easier for customers to secure their data and apps. But that's not easy, Zeus. What are your thoughts on Cisco's security opportunities? >> Yeah, I've been waiting for Cisco go to break up in security a little more than it has. I do think, I was talking with a CSO the other day, Dave, that said to me he's starting to understand that you don't have to have best of breed everywhere to have best in class threat protection. In fact, there's a lot of buyers now will tell you that if you try and have best of breed everywhere, it actually creates a negative when it comes to threat protection because keeping all the policies and things up to date is very, very difficult. And so the industry is moving more to a platform model, right? Now, the challenge for Cisco is how do you get that, the customer to think of the network as part of the platform? Because while the platform model, I think, is starting to gain traction, FloridaNet, Palo Alto, even McAfee, companies like that also have their own version of a security platform. And if you look at the financial performance of companies like FloridaNet and Palo Alto over the past, you know, over the past couple of years, they've been through the roof, right? And so I think an interesting and unique challenge for Cisco is can they convince the security buyer that the network is as important a part of that platform as any other component? If they can do that, I think they can break away from the pack. If not, then they'll stay mixed in with those, you know, Palo, FloridaNet, Checkpoint, and, you know, and Cisco, in that mix. But I do think that may present their single biggest needle moving opportunity just because of how big the security TAM is, and the fact that there is no de facto leader in security today. If they could gain the same kind of position in security as they have a networking, who, I mean, that would move the needle like no other market would. >> Yeah, it's really interesting that they're coming at security, obviously from a position of networking strength. You've got, to your point, you've got best of breed, Okta in identity, you got CrowdStrike in endpoint, Zscaler in cloud security. They're all growing like crazy. And you got Cisco and you know, Palo Alto, CSOs tell us they want to work with Palo Alto because they're the thought leader and they're obviously a major player here. You mentioned FloridaNet, there's a zillion others. We could talk all day about security. But let's bring it back to cloud. We've talked about a number of the piece in Cisco's portfolio, and we haven't really spent any time on full stack observability, which is a big push for Cisco with AppD, Intersight and the ThousandEyes acquisition. And that plays into this equation. But my take, Zeus, is Cisco has a number of cloud knobs that it can turn, it sells core networking equipment to hyperscalers. It can be the abstraction layer to connect on-prem to the cloud and hybrid and across clouds. And it's in a good position with Telcos too, to go after the 5G. But let's use this chart to talk about Cisco's cloud prospects. It's an ETR cut of the cloud customer spending. So we cut it by cloud customers. And they're are, I don't know, 800 or so in the survey. And then looking at various companies performance within that cut. So these are companies that compete, or in the case of HashiCorp, partner with Cisco at some level. Let me just set this up and get your take. So the insert on the chart by the way shows the raw data that positions each dot, the net score and the shared n, i.e. the number of accounts in the survey that responded. The key points, first of all, Azure and AWS, dominant players in cloud. GCP is a distant third. We've reported on that a lot. Not only are these two companies big, they have spending momentum on their platforms. They're growing, they are on that flywheel. Second point, VMware and Cisco are very prominent. They have huge customer bases. And while they're often on a collision course, there's lots of room in cloud for multiple players. When we plotted some other Cisco properties like AppD and Meraki, which as we said, is strong. And then for context, we've placed Dell, HPE, Aruba, IBM and Oracle. And also VMware cloud and AWS, which is notable on its elevation. And as I say, we've added HashiCorp because they're critical partner of Cisco and it's a multi-cloud play. Okay, Zeus, there's the setup. What does Cisco have to do to make the cloud a tailwind? Let's talk about strategy, tailwinds, headwinds, competition, and bottom line it for us. >> Yeah, well, I do think, well, I talked about security being the biggest needle mover for Cisco, I think its biggest challenge is convincing Wall Street in particular, that the cloud is a tailwind. I think if you look at the companies with the really high multiples to their stock, Dave, they're all ones where they're viewed as, they go along with the cloud ride, Right? So the, if you can associate yourself with the cloud and then people believe that the cloud is going to, more cloud equals more business, that obviously creates a better multiple because the cloud has almost infinite potential ahead of it. Now with respect to Cisco, I do think cloud has presented somewhat of a double-edged sword for Cisco. I don't believe the current consumption model for cloud is really a tailwind for Cisco, not really a headwind, but it doesn't really change Cisco's business. But I do think the very definition of cloud is changing before our eyes, Dave. And it's shifting away from centralized clouds. If you think of the way customers bought cloud before, it might have used AWS, it might've used Azure, but it really, that's not really multi-cloud, it's just multiple clouds in which I put things in these centralized resources. It's shifting more to this concept of distributed cloud in which a single application can be built using resources from your private cloud, for AWS, from Azure, from Edge locations, all the cloud providers have built their portfolios to support this concept of distributed cloud and what becomes important there, is a highly agile dynamic network. And in that case with distributed cloud, that is a tailwind for Cisco because now the network is that resource that ties all those distributed cloud components together. Now the network itself has to change. It needs to become a lot more agile and microservices and container friendly itself so I can spin up resources and, you know, in an Edge location, as fast as I can on-prem and things like that. But I do think it creates another wave of innovation and networking, and in that case, I think it does act as a tailwind for Cisco, aside from just the work it's done with the web scalers, you know, those types of companies. So, but I do think that Cisco needs to rethink its delivery model on network services somewhat to take advantage of that. >> At the analyst meeting, Cisco made the point that it does sell to the hyperscalers. It talked about the top six hyperscalers. You know, you had mentioned to me, maybe IBM and Oracle were in there. I always talk about four hyperscalers and only four, but that's fine. Here's my question. Practitioners have told me, buyers have told me, the more money and more workloads I put in the cloud, the less I spend with Cisco. Now, even though that might be Cisco gear powering those clouds, do you see that as a potential threat in that they don't own that relationship anymore and value will confer to the cloud players? >> Yeah, that's, I've heard that too. And I don't, I believe that's true when it comes to general purpose compute. You're probably not buying as many UCS servers and things like that because you are putting them in the cloud. But I do think you do need a refresh the network. I think the network becomes a very important role, plays a very important role there. The variant, the really interesting trend will be, what is your WAM look like? Do you have thousands of workers scattered all over the place, or do you just have a few centralized locations? So I think also, you know, Cisco will wind up providing connectivity within the cloud. If you think of the transition we've seen in other industries, Dave, as far as cloud goes, you think of, you know, F5, a company like that. People thought that AWS would commoditize F5's business because AWS provides their own load balancers, right? But what AWS provides is a very basic, very basic functionality and then use F5's virtual edition or a cloud edition for a lot of the advanced capabilities. And I think you'll see the same thing with the cloud that customers will start buying versions of Cisco that go in the cloud to drive a lot of those advanced capabilities that only Cisco delivers. And so I think you wind up buying more Cisco over time, although the per unit price of what you buy might be a little bit lower. If that makes sense here. >> It does, I think it makes a lot of sense and that fits into the cloud model. You know, you bring up a good point, the conversation with the customer was Rakuten. And that individual was essentially sharing with us, somebody was asking, one of the analysts was asking, "Well, what about the cloud guys? "Aren't they going to really threaten the whole Telco "industry and disrupt it?" And his point was, "Look at, this stuff is not trivial." So to your point, you know, maybe they'll provide some basic functionality. Kind of like they do in a lot of different areas. Data protection is another good example. Security is another good example. Where there's plenty of room for partners, competitors, of on-prem players to add value. And I've always said, "Look, the opportunity "is the cloud players spend 100 billion dollars a year "on CapEx." It's a gift to companies like Cisco who can build an abstraction layer that connects on-prem, cloud for hybrid, across clouds, out to the edge, and really be that layer that is that layer that takes advantage of cloud native, but also delivers that experience, I don't want to use the word seamlessly, but that experience across those clouds as the cloud expands. And that's fundamentally Cisco's cloud strategy, isn't it? >> Oh yeah. And I think people have underestimated over the years, how hard it is to build good networking products. Anybody can go get some silicon and build a product to connect two things together. The question is, can you do it at scale? Can you do it securely? And lots of companies have tried to commoditize networking, you know, White Boxes was looked at as the existential threat to Cisco. Huawei was looked at as the big threat to Cisco. And all of those have kind of come and gone because building high quality network equipment that scales is tough. And it's tougher than most people realize. And your other point on the cloud providers as well, they will provide a basic level of functionality. You know, AWS network equipment doesn't work in Azure. And Azure stuff doesn't work in Google, and Google doesn't work in AWS. And so you do need a third party to come in and act as almost the cloud middleware that can connect all those things together with a consistent set of policies. And that's what Cisco does really well. They did that, you know back when they were founded with routing protocols and you can think this is just an extension of what they're doing just up at the cloud layer. >> Excellent. Okay, Zeus, we're going to leave it there. Thanks to my guest today, Zeus Kerravala. Great analysis as always. Would love to have you back. Check out ZKresearch.com to reach him. Thank you again. >> Thank you, Dave. >> Now, remember I publish each week on Wikibond.com and siliconangle.com. All these episodes are available as podcasts, just search "Braking Analysis" podcast, and you can connect on Twitter at DVallante or email me David.Vallante@siliconangle.com. Thanks for the comments on LinkedIn. Check out etr.plus for all the survey action. This is Dave Vallante for theCUBE insights powered by ETR. Be well and we'll see you next time. (light music)

>>Hi everyone. And welcome to data citizens. Thank you for making the time to join me and the over 5,000 data citizens like you that are looking to become United by data. My name is Jim Cushman. I serve as the chief product officer at Collibra. I have the benefit of sharing with you, the product, vision, and strategy of Culebra. There's several sections to this presentation, and I can't wait to share them with you. The first is a story of how we're taking a business user and making it possible for him or her data, use data and gain. And if it and insight from that data, without relying on anyone in the organization to write code or do the work for them next I'll share with you how Collibra will make it possible to manage metadata at scales, into the billions of assets. And again, load this into our software without writing any code third, I will demonstrate to you the integration we have already achieved with our newest product release it's data quality that's powered by machine learning. >>Right? Finally, you're going to hear about how Colibra has become the most universally available solution in the market. Now, we all know that data is a critical asset that can make or break an organization. Yet organizations struggle to capture the power of their data and many remain afraid of how their data could be misused and or abused. We also observe that the understanding of and access to data remains in the hands of just a small few, three out of every four companies continue to struggle to use data, to drive meaningful insights, all forward looking companies, looking for an advantage, a differentiator that will set them apart from their peers and competitors. What if you could improve your organization's productivity by just 5%, even a modest 5% productivity improvement compounded over a five-year period will make your organization 28% more productive. This will leave you with an overwhelming advantage over your competition and uniting your data. >>Litter employees with data is the key to your success. And dare I say, sorry to unlock this potential for increased productivity, huge competitive advantage organizations need to enable self-service access to data for everyday to literate knowledge worker. Our ultimate goal at Cleaver has always been to enable this self-service for our customers to empower every knowledge worker to access the data they need when they need it. But with the peace of mind that your data is governed insecure. Just to imagine if you had a single integrated solution that could deliver a seamless governed, no code user experience of delivering the right data to the right person at the right time, just as simply as ordering a pair of shoes online would be quite a magic trick and one that would place you and your organization on the fast track for success. Let me introduce you to our character here. >>Cliff cliff is that business analyst. He doesn't write code. He doesn't know Julian or R or sequel, but is data literate. When cliff has presented with data of high quality and can actually help find that data of high-quality cliff knows what to do with it. Well, we're going to expose cliff to our software and see how he can find the best data to solve his problem of the day, which is customer churn. Cliff is going to go out and find this information is going to bring it back to him. And he's going to analyze it in his favorite BI reporting tool. Tableau, of course, that could be Looker, could be power BI or any other of your favorites, but let's go ahead and get started and see how cliff can do this without any help from anyone in the organization. So cliff is going to log into Cleaver and being a business user. >>The first thing he's going to do is look for a business term. He looks for customer churn rate. Now, when he brings back a churn rate, it shows him the definition of churn rate and various other things that have been attributed to it such as data domains like product and customer in order. Now, cliff says, okay, customer is really important. So let me click on that and see what makes up customer definition. Cliff will scroll through a customer and find out the various data concepts attributes that make up the definition of customer and cliff knows that customer identifier is a really important aspect to this. It helps link all the data together. And so cliff is going to want to make sure that whatever source he brings actually has customer identifier in it. And that it's of high quality cliff is also interested in things such as email address and credit activity and credit card. >>But he's now going to say, okay, what data sets actually have customer as a data domain in, and by the way, why I'm doing it, what else has product and order information? That's again, relevant to the concept of customer churn. Now, as he goes on, he can actually filter down because there's a lot of different results that could potentially come back. And again, customer identifier was very important to cliff. So cliff, further filters on customer identifier any further does it on customer churn rate as well. This results in two different datasets that are available to cliff for selection, which one to use? Well, he's first presented with some data quality information you can see for customer analytics. It has a data quality score of 76. You can see for sales data enrichment dataset. It has a data quality score of 68. Something that he can see right at the front of the box of things that he's looking for, but let's dig in deeper because the contents really matter. >>So we see again the score of 76, but we actually have the chance to find out that this is something that's actually certified. And this is something that has a check mark. And so he knows someone he trusts is actually certified. This is a dataset. You'll see that there's 91 columns that make up this data set. And rather than sifting through all of that information, cliff is going to go ahead and say, well, okay, customer identifier is very important to me. Let me search through and see if I can find what it's data quality scores very quickly. He finds that using a fuzzy search and brings back and sees, wow, that's a really high data quality score of 98. Well, what's the alternative? Well, the data set is only has 68, but how about, uh, the customer identifier and quickly, he discovers that the data quality for that is only 70. >>So all things being equal, customer analytics is the better data set for what cliff needs to achieve. But now he wants to look and say, other people have used this, what have they had to say about it? And you can see there are various reviews for different reviews from peers of his, in the organization that have given it five stars. So this is encourages cliffs, a confidence that this is great data set to use. Now cliff wants to look a little bit more detailed before he finally commits to using this dataset. Cliff has the opportunity to look at it in the broader set. What are the things can I learn about customer analytics, such as what else is it related to? Who else uses it? Where did it come from? Where does it go and what actually happens to it? And so within our graph of information, we're able to show you a diagram. >>You can see the customer analytics actually comes from the CRM cloud system. And from there you can inherit some wonderful information. We know exactly what CRM cloud is about as an overall system. It's related to other logical models. And here you're actually seeing that it's related to a policy policy about PII or personally identifiable information. This gets cliff almost the immediate knowledge that there's going to be some customer information in this PII information that he's not going to be able to see given his user role in the organization. But cliff says, Hey, that's okay. I actually don't need to see somebody's name and social security number to do my work. I can actually work with other information in the data file. That'll actually help me understand why our customers churning in, what can I actually do about it. If we dig in deeper, we can see what is personally identifiable information that actually could cause issues. >>And as we scroll down and take a little bit of a focus on what we call or what you'll see here is customer phone, because we'll show that to you a little bit later, but these show the various information that once cliff actually has it fulfilled and delivered to him, he will see that it's actually massed and or redacted from his use. Now cliff might drive in deeper and see more information. And he says, you know what? Another piece that's important to me in my analysis is something called is churned. This is basically suggesting that has a customer actually churned. It's an important flag, of course, because that's the analysis that he's performing cliff sees that the score is a mere 65. That's not exactly a great data quality score, but cliff has, is kind of in a hurry. His bosses is, has come back and said, we need to have this information so we can take action. >>So he's not going to wait around to see if they can go through some long day to quality project before he pursues, but he is going to come up and use it. The speed of thinking. He's going to create a suggestion, an issue. He's going to submit this as a work queue item that actually informs others that are responsible for the quality of data. That there's an opportunity for improvement to this dataset that is highly reviewed, but it may be, it has room for improvement as cliff is actually typing in his explanation that he'll pass along. We can also see that the data quality is made up of multiple components, such as integrity, duplication, accuracy, consistency, and conformity. Um, we see that we can submit this, uh, issue and pass it through. And this will go to somebody else who can actually work on this. >>And we'll show that to you a little bit later, but back to cliff, cliff says, okay, I'd like to, I'd like to work with this dataset. So he adds it to his data basket. And just like if he's shopping online, cliff wants that kind of ability to just say, I want to just click once and be done with it. Now it is data and there's some sensitivity about it. And again, there's an owner of this data who you need to get permission from. So cliff is going to provide information to the owner to say, here's why I need this data. And how long do I need this data for starting on a certain date and ending on a certain date and ultimately, what purpose am I going to have with this data? Now, there are other things that cliff can choose to run. This one is how do you want this day to deliver to you? >>Now, you'll see down below, there are three options. One is borrow the other's lease and others by what does that mean? Well, borrow is this idea of, I don't want to have the data that's currently in this CRM, uh, cloud database moved somewhere. I don't want it to be persistent anywhere else. I just want to borrow it very short term to use in my Tablo report and then poof be gone. Cause I don't want to create any problems in my organization. Now you also see lease. Lease is a situation where you actually do need to take possession of the data, but only for a time box period of time, you don't need it for an indefinite amount of time. And ultimately buy is your ability to take possession of the data and have it in perpetuity. So we're going to go forward with our bar use case and cliff is going to submit this and all the fun starts there. >>So cliff has actually submitted the order and the owner, Joanna is actually going to receive the request for the order. Joanna, uh, opens up her task, UCS there's work to perform. It says, oh, okay, here's this there's work for me to perform. Now, Joanna has the ability to automate this using incorporated workflow that we have in Colibra. But for this situation, she's going to manually review that. Cliff wants to borrow a specific data set for a certain period of time. And he actually wants to be using in a Tablo context. So she reviews. It makes an approval and submits it this in turn, flips it back to cliff who says, okay, what obligations did I just take on in order to work for this data? And he reviews each of these data sharing agreements that you, as an organization would set up and say, what am I, uh, what are my restrictions for using this data site? >>As cliff accepts his notices, he now has triggered the process of what we would call fulfillment or a service broker. And in this situation we're doing a virtualization, uh, access, uh, for the borrow use case. Cliff suggests Tablo is his preferred BI and reporting tool. And you can see the various options that are available from power BI Looker size on ThoughtSpot. There are others that can be added over time. And from there, cliff now will be alerted the minute this data is available to them. So now we're running out and doing a distributed query to get the information and you see it returns back for raw view. Now what's really interesting is you'll see, the customer phone has a bunch of X's in it. If you remember that's PII. So it's actually being massed. So cliff can't actually see the raw data. Now cliff also wants to look at it in a Tablo report and can see the visualization layer, but you also see an incorporation of something we call Collibra on the go. >>Not only do we bring the data to the report, but then we tell you the reader, how to interpret the report. It could be that there's someone else who wants to use the very same report that cliff helped create, but they don't understand exactly all the things that cliff went through. So now they have the ability to get a full interpretation of what was this data that was used, where did it come from? And how do I actually interpret some of the fields that I see on this report? Really a clever combination of bringing the data to you and showing you how to use it. Cliff can also see this as a registered asset within a Colibra. So the next shopper comes through might actually, instead of shopping for the dataset might actually shop for the report itself. And the report is connected with the data set he used. >>So now they have a full bill of materials to run a customer Shern report and schedule it anytime they want. So now we've turned cliff actually into a creator of data assets, and this is where intelligent, it gets more intelligence and that's really what we call data intelligence. So let's go back through that magic trick that we just did with cliff. So cliff went into the software, not knowing if the source of data that he was looking for for customer product sales was even available to him. He went in very quickly and searched and found his dataset, use facts and facets to filter down to exactly what was available. Compare to contrast the options that were there actually made an observation that there actually wasn't enough data quality around a certain thing was important to him, created an idea, or basically a suggestion for somebody to follow up on was able to put that into his shopping basket checkout and have it delivered to his front door. >>I mean, that's a bit of a magic trick, right? So, uh, cliff was successful in finding data that he wanted and having it, deliver it to him. And then in his preferred model, he was able to look at it into Tableau. All right. So let's talk about how we're going to make this vision a reality. So our first section here is about performance and scale, but it's also about codeless database registration. How did we get all that stuff into the data catalog and available for, uh, cliff to find? So allow us to introduce you to what we call the asset life cycle and some of the largest organizations in the world. They might have upwards of a billion data assets. These are columns and tables, reports, API, APIs, algorithms, et cetera. These are very high volume and quite technical and far more information than a business user like cliff might want to be engaged with those very same really large organizations may have upwards of say, 20 to 25 million that are critical data sources and data assets, things that they do need to highly curate and make available. >>But through that as a bit of a distillation, a lifecycle of different things you might want to do along that. And so we're going to share with you how you can actually automatically register these sources, deal with these very large volumes at speed and at scale, and actually make it available with just a level of information you need to govern and protect, but also make it available for opportunistic use cases, such as the one we presented with cliff. So as you recall, when cliff was actually trying to look for his dataset, he identified that the is churned, uh, data at your was of low quality. So he passed this over to Eliza, who's a data steward and she actually receives this work queue in a collaborative fashion. And she has to review, what is the request? If you recall, this was the request to improve the data quality for his churn. >>Now she needs to familiarize herself with what cliff was observing when he was doing his shopping experience. So she digs in and wants to look at the quality that he was observing and sure enough, as she goes down and it looks at his churn, she sees that it was a low 65% and now understands exactly what cliff was referring to. She says, aha, okay. I need to get help. I need to decide whether I have a data quality project to fix the data, or should I see if there's another data set in the organization that has better, uh, data for this. And so she creates a queue that can go over to one of her colleagues who really focuses on data quality. She submits this request and it goes over to, uh, her colleague, John who's really familiar with data quality. So John actually receives the request from Eliza and you'll see a task showing up in his queue. >>He opens up the request and finds out that Eliza's asking if there's another source out there that actually has good is churned, uh, data available. Now he actually knows quite a bit about the quality of information sturdiness. So he goes into the data quality console and does a quick look for a dataset that he's familiar with called customer product sales. He quickly scrolls down and finds out the one that's actually been published. That's the one he was looking for and he opens it up to find out more information. What data sets are, what columns are actually in there. And he goes down to find his churned is in fact, one of the attributes in there. It actually does have active rules that are associated with it to manage the quality. And so he says, well, let's look in more detail and find out what is the quality of this dataset? >>Oh, it's 86. This is a dramatic improvement over what we've seen before. So we can see again, it's trended quite nicely over time each day, it hasn't actually degraded in performance. So we actually responds back to realize and say, this data set, uh, is actually the data set that you want to bring in. It really will improve. And you'll see that he refers to the refined database within the CRM cloud solution. Once he actually submits this, it goes back to Eliza and she's able to continue her work. Now when Eliza actually brings this back open, she's able to very quickly go into the database registration process for her. She very quickly goes into the CRM cloud, selects the community, to which she wants to register this, uh, data set into the schemas community. And the CRM cloud is the system that she wants to load it in. >>And the refined is the database that John told her that she should bring in. After a quick description, she's able to click register. And this triggers that automatic codeless process of going out to the dataset and bringing back its metadata. Now metadata is great, but it's not the end all be all. There's a lot of other values that she really cares about as she's actually registering this dataset and synchronizing the metadata she's also then asked, would you like to bring in quality information? And so she'll go out and say, yes, of course, I want to enable the quality information from CRM refined. I also want to bring back lineage information to associate with this metadata. And I also want to select profiling and classification information. Now when she actually selects it, she can also say, how often do you want to synchronize this? This is a daily, weekly, monthly kind of update. >>That's part of the change data capture process. Again, all automated without the require of actually writing code. So she's actually run this process. Now, after this loads in, she can then open up this new registered, uh, dataset and actually look and see if it actually has achieved the problem that cliff set her out on, which was improved data quality. So looking into the data quality for the is churn capability shows her that she has fantastic quality. It's at a hundred, it's exactly what she was looking for. So she can with confidence actually, uh, suggest that it's done, but she did notice something and something that she wants to tell John, which is there's a couple of data quality checks that seem to be missing from this dataset. So again, in a collaborative fashion, she can pass that information, uh, for validity and completeness to say, you know what, check for NOLs and MPS and send that back. >>So she submits this onto John to work on. And John now has a work queue in his task force, but remember she's been working in this task forklift and because she actually has actually added a much better source for his churn information, she's going to update that test that was sent to her to notify cliff that the work has actually been done and that she actually has a really good data set in there. In fact, if you recall, it was 100% in terms of its data quality. So this will really make life a lot easier for cliff. Once he receives that data and processes, the churn report analysis next time. So let's talk about these audacious performance goals that we have in mind. Now today, we actually have really strong performance and amazing usability. Our customers continue to tell us how great our usability is, but they keep asking for more well, we've decided to present to you. >>Something you can start to bank on. This is the performance you can expect from us on the highly curated assets that are available for the business users, as well as the technical and lineage assets that are more available for the developer uses and for things that are more warehoused based, you'll see in Q1, uh, our Q2 of this year, we're making available 5 million curated assets. Now you might be out there saying, Hey, I'm already using the software and I've got over 20 million already. That's fair. We do. We have customers that are actually well over 20 million in terms of assets they're managing, but we wanted to present this to you with zero conditions, no limitations we wouldn't talk about, well, it depends, et cetera. This is without any conditions. That's what we can offer you without fail. And yes, it can go higher and higher. We're also talking about the speed with which you can ingest the data right now, we're ingesting somewhere around 50,000 to a hundred thousand records per and of course, yes, you've probably seen it go quite a bit faster, but we are assuring you that that's the case, but what's really impressive is right now, we can also, uh, help you manage 250 million technical assets and we can load it at a speed of 25 million for our, and you can see how over the next 18 months about every two quarters, we show you dramatic improvements, more than doubling of these. >>For most of them leading up to the end of 2022, we're actually handling over a billion technical lineage assets and we're loading at a hundred million per hour. That sets the mark for the industry. Earlier this year, we announced a recent acquisition Al DQ. LDQ brought to us machine learning based data quality. We're now able to introduce to you Collibra data quality, the first integrated approach to Al DQ and Culebra. We've got a demo to follow. I'm really excited to share it with you. Let's get started. So Eliza submitted a task for John to work on, remember to add checks for no and for empty. So John picks up this task very quickly and looks and sees what's what's the request. And from there says, ah, yes, we do have a quality check issue when we look at these churns. So he jumps over to the data quality console and says, I need to create a new data quality test. >>So cliff is able to go in, uh, to the solution and, uh, set up quick rules, automated rules. Uh, he could inherit rules from other things, but it starts with first identifying what is the data source that he needs to connect to, to perform this. And so he chooses the CRM refined data set that was most recently, uh, registered by Lysa. You'll see the same score of 86 was the quality score for the dataset. And you'll also see, there are four rules that are associated underneath this. Now there are various checks that, uh, that John can establish on this, but remember, this is a fairly easy request that he receives from Eliza. So he's going to go in and choose the actual field, uh, is churned. Uh, and from there identify quick rules of, uh, an empty check and that quickly sets up the rules for him. >>And also the null check equally fast. This one's established and analyzes all the data in there. And this sets up the baseline of data quality, uh, for this. Now this data, once it's captured then is periodically brought back to the catalog. So it's available to not only Eliza, but also to cliff next time he, uh, where to shop in the environment. As we look through the rules that were created through that very simple user experience, you can see the one for is empty and is no that we're set up. Now, these are various, uh, styles that can be set up either manually, or you can set them up through machine learning again, or you can inherit them. But the key is to track these, uh, rule creation in the metrics that are generated from these rules so that it can be brought back to the catalog and then used in meaningful context, by someone who's shopping and the confidence that this has neither empty nor no fields, at least most of them don't well now give a confidence as you go forward. >>And as you can see, those checks have now been entered in and you can see that it's a hundred percent quality score for the Knoll check. So with confidence now, John can actually respond back to Eliza and say, I've actually inserted them they're up and running. And, uh, you're in good status. So that was pretty amazing integration, right? And four months after our acquisition, we've already brought that level of integration between, uh, Colibra, uh, data intelligence, cloud, and data quality. Now it doesn't stop there. We have really impressive and high site set early next year. We're getting introduced a fully immersive experience where customers can work within Culebra and actually bring the data quality information all the way in as well as start to manipulate the rules and generate the machine learning rules. On top of it, all of that will be a deeply immersive experience. >>We also have something really clever coming, which we call continuous data profiling, where we bring the power of data quality all the way into the database. So it's continuously running and always making that data available for you. Now, I'd also like to share with you one of the reasons why we are the most universally available software solutions in data intelligence. We've already announced that we're available on AWS and Google cloud prior, but today we can announce to you in Q3, we're going to be, um, available on Microsoft Azure as well. Now it's not just these three cloud providers that were available on we've also become available on each of their marketplaces. So if you are buying our software, you can actually go out and achieve that same purchase from their marketplace and achieve your financial objectives as well. We're very excited about this. These are very important partners for, uh, for our, for us. >>Now, I'd also like to introduce you our system integrators, without them. There's no way we could actually achieve our objectives of growing so rapidly and dealing with the demand that you customers have had Accenture, Deloitte emphasis, and even others have been instrumental in making sure that we can serve your needs when you need them. Uh, and so it's been a big part of our growth and will be a continued part of our growth as well. And finally, I'd like to actually introduce you to our product showcases where we can go into absolute detail on many of the topics I talked about today, such as data governance with Arco or data privacy with Sergio or data quality with Brian and finally catalog with Peter. Again, I'd like to thank you all for joining us. Uh, and we really look forward to hearing your feedback. Thank you..

(upbeat music) >> In 2009, Cisco made a major announcement in the form of UCS. It was designed to attack the IT labor problem. Cisco recognized that, data center professionals were struggling to be agile and provide the types of infrastructure services that lines of business were demanding for the modern applications of that day. The value proposition was all about, simplifying infrastructure deployment and management and by combining networking compute and storage with virtualization and a management layer, Cisco changed the game for running applications on premises and the era of converged infrastructure was born. Now fast forward a dozen years, and a lot has changed. The cloud has gone mainstream, forcing new requirements on organizations to bridge their on-prem environments to public clouds and manage workloads across clouds. Now to address this challenge, Cisco earlier this month, announced a series of offerings, that meaningfully expands its original vision, to support the more demanding requirements of today's dev sec ops teams. In particular Cisco, with this announcement is enabling customers to deploy a full stack cloud-like operating model that leverages modern platforms such as Kubernetes, new integrations and advanced tooling to bring automation, visibility and better security for both hybrid and multi-cloud environments. Now the underpinning of this solution, is a new UCS architecture called the X series. Cisco claims this new system gives customers a trusted platform for the next decade to support their hybrid and multi-cloud workloads. Gents, great to see you, welcome. >> Hey, thank you. Good to be here. >> Thanks for having a us Dave. I appreciate. >> My pleasure. Looking forward to this. So look, we've seen the X series announcement and it looks to be quite a new approach. What are the critical aspects of the X series that you want people to understand? Maybe James, and you can take that. >> Sure I think that, you know, overall, there is a lot of change coming in the marketplace, right? We're seeing we're looking at and we're seeing from a technology standpoint, a significant amount of change. Look at CPU's and GPU's, the power draw alone is becoming, you know, it basically at the trajectory, it is, it may be untenable for some, you know, of the current configurations that people are consuming, right? So some of these current architectures just can't deal with that, right? Or at least they can't deal with what's coming in the future. We're also seeing the relevance of other types of architectures like maybe arm to start to become something that our customers want to take advantage of, right? Or maybe want to see how that scale fits into their environment on a totally different level. At the same time, the fabrics are really evolving at lightning speed here, right? So we're seeing PCI express, we've gone from gen three to gen four, gen five is coming in the very near future. We're layering on top of that, things like CXL to take that, that fabric to the next level for capabilities and be able to do things that we couldn't do before. To connect things together, we couldn't do before. Beyond that, we probably are just a few years away from even more exciting developments in the fabric space around some of the high performance low latency fabrics that are that are again on the drawing board today just around the corner. Take that and you, you look at the kind of the evolution of the the admin, right? So we're seeing the admin developer emerge. No longer is this just a guy who's sitting in front of a dashboard and managing systems, keeping them up and down, we're now seeing a whole class of developers that are also administrators, right? So all of this together is starting to push us well beyond what human scale really can manage, what human scale can consume. So, there's a lot of change coming and I think that we're taking a look at that and realizing that something like X series has to be able to deal with that change and the challenges that it brings, but also and do so in a simple manner that we can allow automation orchestration and some of these new capabilities to enhance what our customers can do, not to drown them in technology. >> You know, that taught, that's kind of interesting what James was saying about beyond human scale. I mean, I think my little narrative upfront, it was sort of, hey, we recognize as an IT labor problem. We're going to address that. And it really wasn't about massive scale back then, it is now. We really what we've learned from the cloud guys, right? >> Definitely. I mean, people are moving from pets to cattle to now with containers, they're saying that it's mosquitoes, right? Cause they're so ephemeral, they come and go and on a single host, you could have, you know, hundreds if not thousands of containers. And so the application environment has influenced the infrastructure design and really changed the role of the infrastructure operator to one that necessitates automation, necessitates operations at scale, even on prem everyone's trying to operate in that cloud like model and they're trying to bridge, the big challenge I see is, they're trying to bridge their existing environment big monolithic applications they've got on-prem with those data lakes that they built around them over the past decade, but they're also trying to follow their developers as they go out into the public cloud and innovate there. That's really where the nexus of all the application innovation is. So the IT teams who are already strapped for resources it's not like their budgets are going up every year, are now taking on a new front out in the cloud while they're still trying to maintain the systems that they've built with on-prem. That's the challenge. >> Yeah that's really the hard part and where some of the innovation here is, is anybody that lives in an old house knows that connecting old to new is very challenging much more challenging than building from scratch. But James I wonder if we'd come back to the to the architecture of the X series and what's really unique about it and what's in it for your customers? >> Yes, absolutely. So we're, when were looking at at kind of redesigning this thing from the ground up, we recognized that, you know from a timing standpoint, we're sitting at a place with the development of future fabrics and some of these other technologies that we finally have the opportunity to hit the timing perfectly to start to do composability right. So we've heard a lot of noise, you know in the market for the last several years about composability and how that's going to be the salvation or change the game here. But at the end of the day, the technology hasn't been there in those offerings, right? So we're sitting at the edge of some of the development of those technologies that are going to allow us to do that. And what we've done with X series, is we've taken a construct that we call the UCS X fabric, which is the ability to consume these technologies today as like a effectively a chassis fabric that can allow us to connect resources together within the chassis and future external to the chassis. But it also allows us to take advantage of the change in fabric that's coming. So as fabrics evolve, as we see new technologies like CXL and the PCI express gen five and beyond, come into play here and eventually physical technologies like Silicon Photonix, those are constructs that are going to allow our customers to do some amazing things and we have the construct to be able to consume those. Our goal here is like, to effectively look out at these disruptive technologies on the horizon and make sure that they're not disrupting our customers that we give our customers the ability to disrupt their competitors and to disrupt their markets, but by consuming those technologies in an easy way. >> You know, you didn't use the term future-proof. And I usually don't like that phrase because a lot of times people go that's future-proof and I'm like, well, what's future proof? Well, it's really fast. Well, okay. And in two years, it's going to be, you know really slow compared to everything else. But what you, what you just laid out is an architecture that's really taking advantage of some of these new capabilities that are driving latency down. So that's so, thank you for that. Now, Todd I get how the X series is going to enable customers you know, today I just mentioned the future but how does it play into Cisco's hybrid cloud vision? >> Well I mean, our customers aren't looking for, you know, point solutions or bolt on layers of software to manage across the hybrid cloud landscape. That's the fundamental challenge and so what we're doing with intersite, if you really think about all the systems that we have in our portfolio, like X series, really it's just extensions of our inner site platform. And there we're bridging the gaps between fundamental infrastructure prem, with all of those services that you need to optimize workloads and infrastructure, both in that on-prem environment but also out in the public cloud and even moving up the stack now into serverless. So we know that customers again are trying to bolt together a cohesive environment that allows them to manage those existing workloads on prem but also support the innovation going on out in the cloud and to do that, you have to have services to manage Kubernetes. You need hooks into modern tool chains like a Hashi corks Terraform, we did that a few months back and we recently brought in something we call our service mesh manager that came out of an acquisition of a Bonzai cloud. So what we're doing is, we're kind of spanning that entire spectrum from physical infrastructure, to the workload and that could be extracted in any number of ways either in containers or containers around VMs or bare metal running applications run on bare metal or just virtual machine applications encapsulation. So, you got all these different modalities that customers are going to run applications in and it's our intent to create a platform here that supports all of them, both on their on-prem environment and also all the resources they're managing out in the cloud. So that's a big deal for us. You know, one thing I want to go back to the X series for a second, something James mentioned, right? Is you know as we see subsystems in computing, start to decompose and break apart, you know, we have intersite as the mechanism to put Humpty Dumpty back together again and that's really, I think composability and district's options bar, but that's okay. But so I'll read it together. And like James said, you know be able to take on whatever fabrics, low latency fabrics, ultra low latency fabrics we need in coming years to sew these systems together, we're kind of breaking a barrier that didn't, that wasn't, you know people have trouble breaking through in the past, right? And that's this idea of true infrastructure as code or true software defined infrastructure. Cause now we're talking about being able to apply policy and automation, to the actual construct of a server. How do you build that thing to the needs of the workload? And so if you talk to an SRE or a developer today and you say infrastructure, they're thinking of Kubernetes cluster, but ultimately we want to push that boundary or that frontier between the world software to find it abstracted as far down in the infrastructure, as we can. And with intersite and X fabric and X series, we're taking it all the way down to the individual drive or CPU or ultimately breaking memory apart and sewing that back together. So it's kind of exciting time for us, cause really, pushing that frontier of what is software defined further and further down into the infrastructure and that just gives people a lot more flexibility in what they build. >> So I want to play something back to you and see if it resonates. Essentially, I look at what you just said is you're building a layer across my on-prem, whatever public cloud across clouds at the conventionally, you know, get to the edge, but let's hold off on that, let's park that for now. But that layer obstructs the underlying technical complexity and allows that infrastructure to be, you said programmable, infrastructure is code essentially. So that's one of my other questions, it's like, how programmable is this infrastructure, you know, today and in the future? But is that idea of an abstraction layer kind of how you're thinking about hybrid and multi-cloud? >> It is in terms of the infrastructure that customers are going to run on prem right in the public cloud the cloud providers are already abstracting that for them. And so what we want to do is bring that same type of public cloud experience to managing infrastructure on prem. So being able to have pools of resources that you allocate out to workloads, shifted as things change. So it's absolutely a cloud-like approach to on-prem infrastructure and you know, one of the things I like to say is, you know, friends don't let friends, build their own private cloud platforms from scratch, right? We're productizing this, we're bringing it as a cohesive system that customers don't need to engineer on their own. They can focus on their operations and James actually, he's a pilot, and one of the things he observed about Intersight a couple of years ago was, this idea of Intersight as a co-pilot and kind of, you know, adding a person to your team almost when you have intersite in your data center, because some very, what feels like rudimentary things are incredibly impactful day-to-day for our customers. So we have recommendation engines. If it, if like, you know, maybe it says some interplay between bios and firmware and operating system and we know that there's an issue there rather than letting customers stumble upon that on their own we're going to flag it, show them the correction, go implement it for them. So that it starts to feel a lot more like what they're accustomed to in a public cloud setting where the system has some intelligence baked in, the system is kind of covering them and watching their back and acting like a co-pilot day-to-day operations. >> Okay, so I get that, you know, the cloud guys will abstract the complexity you guys are focused on prem, but is it, so my question then is multi-cloud across clouds because we have some cloud providers, you know you're partners with Google they do some things with Antho, so I know Microsoft with Ark, but even near-term. Should we think about Cisco as playing that role of my, across cloud, you know, partner if you will? >> Absolutely. You know, cloud agnosticism is core to our approach because we know that, you know if you dial the clock way back to the early odds, right? When cloud first started emerging it was kind of an efficiency play. And you had folks like Nicholas Carr, right? The author that they put out the big switch, kind of envisioning a world where there'd be this ultimate consolidation to maybe one or two or three cloud platforms worldwide. But what we're seeing, you know we had data sovereignty kind of emerge over the past decade but even the past year or two, it's now becoming issues of actual cloud sovereignty. So you have governments in Australia and in India and in Europe actually asserting control over the cloud providers and services that can be used by their public sector organizations and so that's just leading to actually cloud fragmentation. It's not nearly as monolithic of future as we thought it would be. It's a lot of clouds and so as customers want to move around geographically or if they want to go harvest innovation that maybe Google is really good at something like machine vision, or they want to use AWS or Azure for different applications that they're going to go build. We're seeing customers really being put in a place where they're going to deal with multiple cloud providers and the data supports that. So it's definitely our approach especially on the networking technology side to make it very easy for our customers to go out and connect these different clouds and not have to repeat the integration process every time they want to go, you know, start using another public cloud provider. So that's absolutely our strategies to be very agnostic and build everything in mind for customers they're going to be using in multiple providers. >> Thank you for that touch. So James, I want to come back and talk a little bit about sort of your competitive posture here. I mean, you guys, when you made the announcement, I inferred that you were feeling like you were in a pretty good position relative to the competition that you were putting forth, not just you know, core infrastructure in hardware and software but also all these other components around it that we talked about, observability extending out to the, you know, beyond the four walls of my data center, et cetera. But talk a little bit about why you think this gives you such competitive advantage in the marketplace. >> Well I mean, I think first of all, back to where Todd was going as well, is that, you know if you think about trying to be, to work in this hybrid cloud world, that we're clearly living in, the idea of burrowing features and functions as far down the stack as possible, doesn't make a lot of sense, right? So intersite is a great example. We want to manage and we want to orchestrate across clouds, right? So how are we going to have our management and infrastructure services buried into the chassis, down at the very lowest level, that doesn't make sense. So we elevated our, you know, our operating model to the cloud, right? And that's how we manage across clouds from the cloud. So, building a system and really we've done this from the ground up with X series, building a system that is able to take advantage of all these two technologies. And you mentioned, you know, how being future proof was probably you know, a derogatory term almost and I agree with you completely. I think we're future ready. Like, we're ready to embrace it because we're not trying to say that nothing is going to change beyond what we've already thought of, we're saying, bring it on. We're saying, bring on that change because we're ready for it. We've we can accommodate change. We, we're not saying that the technology we have today is to going to ride us for 10 years, we're saying,, we're ready for the next 10 years of change. Bring it. We can do that in a simple way. That is, you know, I think, you know going to give us the versatility and the simplicity to allow the technology to go beyond human scale without having to you know drown our customers in administrative duties, right? So that co-pilot that Todd mentioned is going to be able to take on a lot more of the work, just like an airplane where you know, the pilot has functionality that he has to absolutely be part of and those are the our developers, right? We want those admin developers to develop, to build things and to do things and not get bogged down in the minutiae that exists. So I think competitively, you know, our architecture top to bottom, you know, all the way up the stack, all the way to the bottom is unique and it is focused on not just the rear view mirror but what's coming in the future. >> So my takeaway there is that, okay, I get it. The new technologies will come along but this architecture is the architecture for the decade. You're not going to have to redo the architecture in a few years. That's really the key point here. Todd, I'll give you last word might just taking some notes here and takeaways that I heard, I heard upfront. Chip diversity really take advantage of all the innovations that are coming out. You're ready for that. You're kind of blurring the lines between blade and rack, giving some optionality there. Scale is a big theme. I mean, the cloud has brought that in and, you know people want to scale, they don't want to be, you know provisioning lawns all day and they won't be able to scale if that's what their job is. Developer friendly, particularly as it relates to infrastructure as code. And you've got a roadmap. So Todd, that's my summary. I'll give you the last word. >> No, it's really good. I mean, you hit it, right. We're thinking about this holistic operating environment that our customers are building for hybrid cloud and we're pre-engineering that environment for them. So our Intersight platform, all of our systems that connect to that, are really built to tackle that hybrid environment from end to end, and with systems like X series, we're giving them a more simple, efficient landing spot for their workloads on prem but crucially it's fully integrated with this hybrid cloud platform so as they have workloads on prem and workloads in the cloud, it's kind of a transparent environment between those two, between those two, two worlds there. So bringing it together so that our customers don't have to build it themselves. >> Excellent. Well, gents thanks so much for coming on theCUBE and sharing the details of this announcement. Congratulations, I know how much work and thought goes into these things, really looking forward to its progress and adoption in the marketplace. Appreciate your time. >> Thank you. >> Thanks for time. >> And thank you for watching this cube conversation. This is Dave Vellante. We'll see you next time. (upbeat music)

>> From around the globe it's theCube. Presenting Future Cloud. One event, a world of opportunities. Brought to you by Cisco. >> We're here with Vikas Ratna, who's the director of product management for ECS at Cisco and James Leach is the director of business development for UCS at Cisco as well. We're going to talk about computing in the age of hybrid cloud. Welcome gentlemen, great to see you. >> Thank you. >> Thank you. >> Vikas let's start with you and talk a little bit about computing architectures. We know that they're evolving, they're supporting new data intensive and other workloads, especially as high-performance workload requirements, what's Cisco's point of view on all this? And specifically, I'm interested in your thoughts on fabrics, I mean, it's kind of your wheelhouse, you've got accelerators, What are the workloads that are driving these evolving technologies and how is it impacting customers? What are you seeing? >> Sure, Dave. First of all, very excited to be here today. You're absolutely right. The pace of innovation and foundational platform ingredients have just been phenomenal in recent years. The fabric, accelerators, the drives, the processing power, the core density all have been evolving at just an amazing pace and the pace will only pick up further, but ultimately it is all about applications and the way applications leverage those innovations. And we do see applications evolving quite rapidly. The new classes of applications are evolving to absorb those innovations and deliver much better business values, very, very exciting times, Dave, but talking about the impact on the customers, well these innovations have helped them pretty positively. We do see significant challenges in the data center with a point product based approach of delivering these platform innovations to the applications. What has happened is these innovations today are being packaged as point products to meet the needs of a specific application. And as you know, the different applications have their different needs. Some applications need more tributes, others need more memory, yet others need, you know, more cores. Some need different kinds of fabrics. As a result, if you walk into a data center today, it is pretty common to see many different point products in the data center. This creates a manageability challenge. Imagine the aspect of managing, you know, several different form factors, one you, to you, purpose-built servers or the variety of, you know, blade form factor. You know, this reminds me of the situation we had before smartphones arrived. You remember the days when you, when we used to have a GPS device for navigation system, a cool music device for listening to the music, a phone device for making a call, camera for taking the photos. Right? And we were all excited about it. It's when the smartphones arrived that we realized all those cool innovations could be delivered in a much simpler, much convenient, and easy to consume it through one device and, you know, and that could completely transform our experience. So we see the customers who are benefiting from these innovations to have a way to consume those things in a much more simplistic way than they are able to do it today. >> And I like, look, it's always been about the applications, but to your point, the applications are now moving at a much faster pace. The customer experience is, expectation, is way escalated. And when you combine all these, I love your analogy there Vikas, because when you combine all these capabilities, it allows us to develop new applications, new capabilities, new customer experiences. So that's the, I always say, the next 10 years, they ain't going to be like the last. And James, public cloud obviously is heavily influencing compute design and customer operating models. You know, it's funny, when the public cloud first hit the market, everyone, we were swooning about oh, low cost, standard off-the-shelf servers, you know, and storage devices, but it quickly became obvious that customers needed more. So I wonder if you could comment on this. How are the trends that we've seen from the hyperscalers, how are they filtering into on-prem infrastructure and maybe, you know, maybe there's some differences there as well that you could address? >> Absolutely. So, you know, I'd say first of all, quite frankly, you know, public cloud has completely changed the expectations of how our customers want to consume compute, right? So customers, especially in a public cloud environment, they've gotten used to, or, you know, come to accept that they should consume from the application out, right? They want a very application-focused view, a services-focused view of the world. They don't want to think about infrastructure, right? They want to think about their application. They want to move outward, right? So, this means that the infrastructure basically has to meet the application where it lives. So what that means for us is that, you know, we're taking a different approach. We've decided that, you know, we're not going to chase this, you know, single pane of glass view of the world, which, you know, frankly our customers don't want. They don't want a single pane of glass. What they want is a single operating model. They want an operating model that's similar to what they can get with the public cloud, but they want it across all of their cloud options. They want it across private cloud, across hybrid cloud options, as well. So what that means is they don't want to just consume infrastructure services. They want all of their cloud services from this operating model. So that means that they may want to consume infrastructure services for automation orchestration, but they also need Kubernetes services. They also need virtualization services. They may need Terraform, workload optimization. All of these services have to be available from within the operating model, a consistent operating model, right? So it doesn't matter whether you're talking about private cloud, hybrid cloud, anywhere, where the application lives doesn't matter. What matters is that we have a consistent model, that we think about it from the application out, and frankly, I'd say, you know, this has been the stumbling block for private cloud. Private cloud is hard, right? This is why it hasn't been really solved yet. This is why we had to take a brand new approach. And frankly, it's why we're super excited about X Series and intersight as that, you know, operating model that fits the hybrid cloud better than anything else we've seen. >> This is a Cube first, first time's a technology vendor has ever said that it's not about a single pane of glass because I've been hearing for decades we're going to deliver a single pane of glass. It's going to be seamless and it never happens. It's like a single version of the truth. It's aspirational. And it's just not reality. So can we stay on the X Series for a minute, James, maybe in this context, but in the launch that we saw today, it was like a fire hose of announcements. So, how does the X Series fit into the strategy with intersight, and hybrid cloud in this operating model that you're talking about? >> Right. So, I think it goes hand-in-hand, right? The two pieces go together very well. So we have, you know, this idea of a single operating model that is definitely, you know, something that our customers demand, right? It's what we have to have, but at the same time we need to solve the problems Vikas was talking about before, we need a single infrastructure to go along with that single operating model. So no longer do we need to have silos within the infrastructure that give us different operating models or different sets of benefits, when you want infrastructure that can kind of do all of those configurations, all those applications. And then, you know, the operating model is very important because that's where we abstract the complexity that could come with just throwing all that technology at the infrastructure. So that, you know, this is, you know, the way that we think about it is the data center is not centered, right? It's no longer centered. Applications live everywhere. Infrastructure lives everywhere. And, you know, we need to have that consistent operating model, but we need to do things within the infrastructure as well to take full advantage, right? So we want all the SaaS benefits of a CICD model of, you know, the intersight can bring, we want all of that, you know, proactive recommendation engine with the power of AI behind it, we want the connected support experience. We want all of that, but we want to do it across a single infrastructure. And we think that that's how they tie together. That's why one or the other doesn't really solve the problem, but both together. That's why we're here. That's why we're super excited. >> So Vikas, I make you laugh a little bit. When I was an analyst at IDC, I was a bit deep into infrastructure, And then when I left, I was doing, I was working with application development heads. And like you said, infrastructure, it was just a roadblock, but it was so the tongue-in-cheek is when Cisco announced UCS a decade ago, I totally missed it. I didn't understand it. I thought it was Cisco getting into the traditional server business. And it wasn't until I dug in that I realized that your vision was really to transform infrastructure deployment and management. And change the model. It was like, okay, I got that wrong. But, so let's talk about the, the ecosystem and the joint development efforts that are going on there. X Series, how does it fit into this converged infrastructure business that you've built and grown with partners? You've got storage partners like NetApp and Pure. You got ISV partners in the ecosystem. We see Cohesity, it's been a while since we hung out with all these companies at the Cisco live, hopefully next year, but tell us what's happening in that regard. >> No, absolutely. I'm looking forward to seeing you in the Cisco live next year, Dave. Absolutely. You brought up a very good point. UCS is about the ecosystem that it brings together. It's about making our customers bring up the entire infrastructure, from the core foundational hardware all the way to the application level so that they can all go off and running pretty quick. That converse infrastructure has been one of the cornerstones of our strategy, as you pointed out, in the last decade. And I'm very glad to share that conversed infrastructure continues to be a very popular architecture for several enterprise applications even today. In fact, it is the preferred architecture for mission critical applications, where performance, resiliency, latency, are the critical requirements. They are almost de facto standards for large scale deployments of virtualize and business critical databases and so forth. With X Series, with our partnerships, with our restorative partners, those architectures will absolutely continue and will get better. But in addition, it's a hybrid cloud world. So we are now bringing in the benefits of conversed infrastructure to the world of hybrid cloud. We'll be supporting the hybrid cloud applications now with the CA infrastructure that we have built together with our strong partnership with the store as partners to tell you with the same benefits to the new age applications as well. >> Yeah and that's what customers want, they want that cloud operating model. Right? Go ahead, please. >> I was just going to say, you know, that the CA model will continue to thrive. It will transition out, it will expand the use cases now for the newer use cases that we were beginning to see, Dave, absolutely. >> Great. Thank you for that. And James, like I said earlier today, we heard this huge announcement, a lot of parts to it. And we heard, you know, KD talk about this initiative is, it's really computing built for the next decade. I mean, I like that because it shows some vision and that you've got, you know, a roadmap, that you've thought through the coming changes in workloads and infrastructure management and some of the technology that you can take advantage of beyond just the, you know, one or two product cycles. So, but I want to understand what you've done here specifically that you feel differentiates you from other competitive architectures in the industry. >> Sure. You know, that's a great question. number one. Number two, I'm frankly a little bit concerned at times for customers in general, for our customers, customers in general, because if you look at what's in the market, right? These rinse and repeat systems that were effectively just rehashes of the same old design, right? That we've seen since before 2009 when we brought UCS to market, these are what we're seeing over and over and over again, that's not really going to work anymore, frankly. And I think that people are getting lulled into a false sense of security by seeing those things continually put in the market. We've rethought this from the ground up because frankly, you know, future-proofing starts now, right? If you're not doing it right today, future-proofing isn't even on your radar because you're not even, you're not even today-proofed. So we've rethought the entire chassis, the entire architecture, from the ground up. Okay. If you look at other vendors, if you look at other solutions in the market, what you'll see is things like, you know management inside the chassis. That's a great example. Daisy chaining them together. Like, who needs that? Who wants that? Like, that kind of complexity is, first of all, it's ridiculous. Second of all, if you want to manage across clouds you have to do it from the cloud, right? It's just common sense. You have to move management where it can have the scale and the scope that it needs to impact, you know, your entire domain, your world, which is much larger now than it was before. We're talking about true hybrid cloud here. Right? So, we had to, you know, solve certain problems that existed in the traditional architecture. You know, I can't tell you how many times I heard you know, talk about, you know, the mid plane is a great example. Well, you know, the mid plane in a chassis is a limiting factor. It limits us on how much we can connect or how much bandwidth we have available to the chassis. It limits us on air flow and other things. So how do you solve that problem? Simple. Just get rid of it. Like we just, we took it out, right? It's now no longer a problem. We designed an architecture that doesn't need it. It doesn't rely on it, no forklift upgrades. So as we start moving down the path of needing liquid cooling, or maybe we need to take advantage of some new high performance, low latency fabrics. We can do that with almost no problem at all, right? So we don't have any forklift upgrades. Park your forklift on the side. You won't need it anymore because you can upgrade granularly. You can move along as technologies come into existence that maybe don't even exist today. They may not even be on our radar today to take advantage of but I like to think of these technologies. You know, they're really important to our customers. These are, you know, we can call them disruptive technologies. The reality is that we don't want to disrupt our customers with these technologies. We want to give them these technologies so they can go out and be disruptive themselves, right? And this is the way that we've designed this, from the ground up, to be easy consume and to take advantage of what we know about today and what's coming in the future that we may not even know about. So we think this is a way to give our customers that ultimate capability, flexibility, and future-proofing. >> I like that phrase, true hybrid cloud. It's one that we've used for years. But to me, this is all about that horizontal infrastructure that can support that vision of what true hybrid cloud is. You could support the mission critical applications. You can develop on the system and you can support a variety of workloads. You're not locked into, you know, one narrow stovepipe. And that does have legs. Vikas and James, thanks so much for coming on the program. Great to see you. >> Thank you, we appreciate the time. >> Thank you. >> And thank you for watching. This is Dave Volante for theCube, the leader in digital event coverage. (uplifting music)