• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Bb2373 gray _virtualize_you_dc_with_flex_fabric_final
 

Bb2373 gray _virtualize_you_dc_with_flex_fabric_final

on

  • 673 views

 

Statistics

Views

Total Views
673
Views on SlideShare
673
Embed Views
0

Actions

Likes
0
Downloads
76
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Building Cloud-Optimized Networks Enterprises are turning to Cloud to accelerate business innovation, improve agility and contain costs. These highly dynamic emerging Cloud use models coupled with an exploding requirement to accommodate increasingly virtualized IT environments are having profound effects on existing enterprise network designs. This session will detail how HP’s FlexNetwork solutions allow enterprises to securely deploy and centrally orchestrate cloud-optimized architectures that scale from the data center to the network edge.What is the impact of cloud on the network?I’m sure of one thing … THE NETWORK is NOT just plumbing … (don’t be fooled by the SEXY cloud ICONs)I was recently asked this question . . . And with much of the cloud hype being centered on software, storage, virtualization and Xaas, I thought it might be helpful to pull together a quick post around the implications of cloud computing on network. As you turn to cloud computing to accelerate business innovation and contain costs, you need to be keenly aware of how cloud (and virtualization) reshapes the way applications are deployed and consumed and influences your data center network design. While the deployment types may vary—private, public or hybrid cloud—the higher performing compute engines that drive these new cloud use modules have much in common. For example: increasingly powerful multi-core-processor (blade) servers, higher-bandwidth/density 10 GbE interfaces, driving virtual machine scaling measured in the thousands all deployed in a single rack. These larger-scale solutions dramatically increase network performance requirements at the server edge and across the extended network. More over, virtualization and vMotion/Live Migration introduce high-volume machine-to-machine traffic flows that blur the traditional boundaries between the network and server administrators and physical and virtual worlds.The key take-away I want to convey is that customers can start taking steps TODAY to “cloud optimized” their networks in a very migratory manner in the DC, across the enterprise etc … (depending on where they are at with “cloud”) … while at the same time they are improving their overall IT environment an operating (cloud or no cloud). … - but by partnering with HP … we have the products and vision that can help get you to where you want to go.You can start today! Revisit existing network design assumptionsTake an “Application Centric” perspective - Lots of buzz in the DC - but don’t forget the rest of your networkTactical IT networking best practices can be made along the wayHP can help you design and build your “network” You can start today! Revisit existing network design assumptionsTake an “Application Centric” perspective - Lots of buzz in the DC - but don’t forget the rest of your networkTactical IT networking best practices can be made along the wayHP can help you design and build your “network”
  • Evolving enterprise networks to support cloud models So what’s my point? The bottom line is that contemporary data center networks designed to support siloed IT architectures simply aren’t designed meet the performance, security, availability and agility requirements of cloud. As IT/network operators begin to think (or re-think) about how you will build and design you networks moving forward to accommodate emerging cloud use models, you would be well served to consider HP’s FlexNetwork Architecture. HP FlexNetwork Architecture: why it’s right for supporting cloud computing Our HP FlexNetwork Architecture allows enterprises to securely deploy and centrally orchestrate cloud-optimized architectures that scale from the data center to the network edge. HP FlexNetwork enables the construction of flatter, simpler data center networks to support the bandwidth-intensive, delay-sensitive server-to-server virtual machine and workload traffic flows that accompany cloud.The benefits of HP FlexNetwork Architecture include: Massive architectural design simplification, connecting users to applicationsHigh-performance, low-latency, ultra-resilient virtualized networking fabric Open standard-based networks designed to lower operational complexity and cost Learn more HP’s Building Cloud-Optimized Data Center Networks is a helpful resource if you are looking at how to best “cloud-optimize” your network to address the new generation of requirements that cloud demands. You might also want to watch these two videos:  >>The Future of the Cloud>> SHI Delivering Cloud Services by Changing the Rules of Networking with help from HP
  • Singtel LTE, 4G … 65 Mbps – fixed mobile convergence2/3rds of the worlds mobile traffic will be video by 2015 – immersive collaboration … pervasive video4 top technology trends for 2012: What do they mean for networking?  Some related trends … 1. Software-based Networking – As we know, networking is more than just transporting bits between the user and the application. As transport cost per-bit drops drastically, networks are now adding functionality to make them more and more intelligent. The software aspect seems to be taking two different flavors. One to transport bits faster to reduce cost per bit by using FPGA/ASIC for forwarding and software-based controller to better utilize the traffic/network capabilities and lower costs. The other to add features to increase the value of what networks deliver. This includes features like content delivery, security, load balancing and WAN optimizations that can be in software run on general-purpose processors. In many instances the services will actually be run on virtual machines (VMs), so as to enable easy scale-out as the traffic/ users increase.  2. Big Data and Analytics – Business intelligence (BI) and real-time data analytics for large data sets are high on the priority for CIO’s. While most human data is structured; machine-to-machine data is totally unstructured and growing. It is this data that is most interesting for BI. To do ETL on the unstructured data and to then store in an RDBMS is a resource hog, if not impossible. Hadoop is a framework for distributed processing of such unstructured data in a clustered system. Organizations like Walmart have been extensively using intelligent analytics on this data for gaining a leg-up over their competitors, and most others now understand the business benefits of the same. Big Data frameworks like Hadoop (which recently reached “release 1.0.0” after six years of gestation) however have some typical requirements on the network because of their large but bursty nature and using TCP for data transport. Processing such workloads need a network that can provide latency/ loss/ jitter bounds, besides high bandwidth. In a shared network, these also require the ability to clearly separate out traffic with different characteristics from one-another. In the network front this means the ability to have bigger buffers to prevent packet loss, which affects TCP.   3. Enterprise Cloud – There have been a lot of discussions about enterprises using the public clouds and services on the public cloud. The current thought process seems to have come to the fact that for IaaS, enterprises should own the base and use the public cloud for the spikes (the infrastructure requirements that are seasonal and at times hard to predict).  I envision the enterprise-class cloud architectures need to be designed to work around failures. Future enterprise-class public clouds will differentiate by the ability to provide some level of SLA and guarantees within the cloud data center. In the same way, MPLS is able to differentiate when compared to Direct Internet Access connectivity for enterprises. It also means a greater level of security, auditing, monitoring and privacy to protect critical enterprise data. 4. Consumerization of IT – This term seems to mean a lot of different things to different organizations. For the IT organization, it is a way to regain control of enterprise data, which was leaking because employees used personal devices for transmitting enterprise data. This is changing the enterprise software landscape where “consumerization” means more than just using consumer applications for enterprise. In a lot of cases it signifies borrowing concepts like intuitive UI to design enterprise applications. On the networking front one of the biggest changes it brings is the complete reliance on wireless as most new consumer devices like tablets and smart-phones, do not have a Ethernet interface and hence totally rely on wireless. It means support and control of varied devices from different users without compromising enterprise data – so stricter yet easier to use security. 
  • Design limitations not optimized for emerging traffic patternsBW explosion, N/S to E/W, Hub Spoke to meshDesign limitations not optimized for emerging traffic patterns/volumeLimited network visibility/control/security (E-E, physical and virtual)Inconsistent user experience, application performance/availability Dislocation between Application/VM & Network provisioning modelsAdding more boxes/bandwidth doesn’t helpThe WAN …Big pipe – little pipe issueThe need for Intelligence at the (WAN) edgeUnpredictable traffic patterns (back-haul, any to any) Poor Application PerformanceOptimized Application PerformanceDeployment/management complexity
  • You need to take a holistic end-end view … Certainly lots of action in the DC where the focus has been (needs to be)But don’t forget the users … and there locations, use/access models … in the campus, branch, mobile use . BYOD etc … These can’t be dealt in silos … this would scale, unmanageable …
  • Workloads will be virtualized by the end of 2016Virtualization is a Networking Game Changer (key points on the slides) … NOT just about need 1/10 GbE access – CUSTOMERS NEED TO RETHINK THEIR CURRENT NETWORK DESIGNSThe consequence of changing application deployment and increased use of VM migration will mean that traffic patterns in the data center network are changing from being predominantly client/server (north-south) to a significant level of server-to-server (east-west) flows. Example - VM mobility requires a flat Layer 2 network It can burst up to 9 Gbps and will introduce long-duration data transfer between servers. This means that network design must change. Traditional three- and four-tier data center network architectures focus on aggregating traffic flows from servers to users. GARTNER: “Network planners should reconsider their existing designs to facilitate better internal traffic flows. Reducing the number of tiers in the network will reduce the number of network hops; HP ESSN LEVERAGE POINT … HP SERVER/VM LEADERSHIP
  • Federated Applications and Virtualization driving increased East-West server-to-server traffic…Multi-tier Legacy NetworkLimited capacity to secure servers, VMs, and appsFACT: 75% of application traffic in emerging cloud data centers is confined to within the rack in which it was generated.Question: Why would you design a network which requires the traffic to be switched across many low performing, high latency external hops? Federated Applications and Virtualization driving increased East-West server-to-server traffic…Multi-tier Legacy NetworkOversubscribedNo local switchingMultiple network hopsHigh Latency High cost, complexityLegacy hierarchical data center networks were designed to support client-server applications and can’t meet the performance and scalability requirements of the new virtualized data center and federated applications.Server virtualization initiatives are reshaping data center traffic flows, increasing bandwidth densities at the server edge and pushing conventional data center networks to the brink. Server virtualization will expand to support 50% of workloads by 2012 (Gartner)70% budget spent on operations (corporate quote)
  • Traditional rack server designs 16 rack servers with 1 fully loaded BladeSystem C7000 enclosure. The rackmount servers would need a pair of ToR switches and the C7000 enclosure would have 2 VC modules. You can run up to 8 10GbE cables out of each module, but most commonly each module has one stacking cable to the another module and one 10GbE uplink cable out of the enclosure to a distribution switch someplace. 100% of the traffic need to be routed to outside/upstream to L2/3 devices/layers – adding latency and poor user/application experience80% of the traffic stays “local” to the enclosure – delivering much lower latency and a superior user/application experienceHPVirtual Connect modules in the back of the enclosures, this allows us to also apply Insight Orchestration to enable pre-packaged automation, or apply the Virtual System reference models, or VDI.  The power savings were simply looking at the switch component of not having TOR and EOR and move to just end of room.  The power comparison was the number of CISCO switches used today compared against the HP approach of flattening the network with HP switches.  As well as the reduction in switches providing a reduction in power consumption we found during the analysis that some HP switches require less than half the power a CISCO switch requires. Don’t forget in terms of savings, we are have not included; air conditioning power savings, cabling cost reduction, support reduction, management FTE reduction, etc. So there is still lots of savings to be had even if the cost per KwH is reduced.  And the value was shared so that someone could come up with their won savings value based on the cost of electricity.
  • VM mobility requires a flat Layer 2 network It can burst up to 9 Gbps and will introduce long-duration data transfer between serversA single multicore x86 server can support 20+ VMs … with 100-1,000 servers … 20-40X VM sprawl across the DC … with lots of workload mobility $350 per 10 GbE LOMVirtualized and Cloud Optimized NetworkingMassive architectural simplification – connecting users to applicationsHigh performance, low latency, ultra-resilient virtualized networking fabric Open standard based networks designed to lower operational complexity/costEnterprises are turning to the Cloud to accelerate business innovation, improve business agility and contain costs. Cloud computing reshapes the way applications are deployed and consumed and influences data center network designs. Virtualization is a fundamental element/building block for Cloud and is having profound effects on existing enterprise networks; Due to the order of magnitude increased in raw bandwidth that will be needed (supporting multi-GbE VM/workload mobility)Along with dramatic changes in increased server-server traffic patterns forcing customers to rethink current (legacy) network designs  HP FlexNetwork solutions address these challenges by delivering; • Flatter and more efficient 10/40G data center networks with fewer layers, equipment and cabling, and greater port densities • High performance, low latency intra-data center connectivity for VM migration and bandwidth-intensive server-to-server trafficeReducing VM workload mobility transit time (by 40%)Doubling (2X) VM application performanceImproving VM disaster recovery times by up to 500x• Virtualization-aware security to partition multi-tenant environments and isolate virtual resources• Optimizing WAN performance for the highest quality end-user and application experiences• Orchestrating thousands of physical and virtual resources from a single pane of glass (IMC)
  • 2/3rds of the worlds mobile traffic will be video by 2015Rich WAN/routing servicesQoS, MPLS, IPv4/6, security, Multicast, WAN optimization, GREBig pipe – little pipe issueThe need for Intelligence at the (WAN) edgeUnpredictable traffic patterns (back-haul, any to any) Performance/prioritization/QoSApplication/WAN optimizationDeployment/management complexity
  • 50 Billion devices will connect to wireless networks by the year 2020Links in a chain … supply and demand…Singtel LTE, 4G … 65 Mbps – fixed mobile convergence2/3rds of the worlds mobile traffic will be video by 2015 – immersive collaboration … pervasive video10XIncrease in network capacity required to support new wave of business video applications-------------------------Increased workforce mobilityHigh levels of mobility driving demand for integrated enforcement of access control, security policies and management Proliferation of cloud services, multi-media applications and SaaSCloud services, Multi-media and SaaS are driving demand for high bandwidth/higher user density applications with better capacity. Complexity of managementSpiraling IT footprint/costsEnterprises want to meet the increasing demand for mobile local area network access while lowering the cost of ownership to deal with the user device sprawl caused by the consumerization of IT with employees having a notebook, tablet and smartphone for business use. Lifetime waranteeEnterprises want a converged wired and wireless infrastructure for consistent enforcement of access control, security policies and management.High bandwidth mobility services are needed for multi-media and hi-res medical imaging applications such as PACSEnterprises want to meet the increasing demand for mobile local area network access while lowering the cost of ownership to deal with the user device sprawl caused by the consumerization of IT with employees having a notebook, tablet and smartphone for business useSimplified management with consistent policy enforcement across wired and wireless infrastructures.Ensuring quality of service for concurrent users and bandwidth intensive applicationsOn line learning – students all accessing course material simultaneously Digital imaging for healthcare – bandwidth intensive Double the number of users per access point Up to 50% improvement in performanceCustomers forced to use many different management tools.Single-pane-of-glass managementReduction of OPEX: training on only one application & troubleshooting and event correlation – events in real time across wired/wirelessWired, wireless solution that has a single security approachIntegrated security for client authentication regardless of method of accessVolume of devices that people are attaching to the Wi-Fi network is also a driving force to why people are investing in this space as well as increase use of “cloud” implementations.
  • A Citrix VDI thin client can consume as much as 500 Mbps of traffic … a typical branch with a T-1 (1.5 Mbps) and maybe have 20+ usersThe HP branch office networking solution converges infrastructure needed in branch offices and simultaneously delivers an open platform for best-of-breed 3rd party network applications to dramatically simplify branch office deployments, centralize management, improve business productivity and reduce IT costs. The branch solution is a component in the HP end-to-end enterprise network infrastructure, which optimizes the network for secure, reliable, high performance application delivery, and a cornerstone for converged infrastructure functionality for the extended enterprise.Converge connectivity: Integrated solution simplifies branch networking and application delivery, integrated security and unified managementOptimize application delivery: Headquarters-quality access and productivity for the branch – with reliable, secure and high-performance application deliveryImprove agility with Best of breed applications: Application module delivers an open platform for 3rd party integration, simplifying application delivery and eliminating costly vendor lock-in , modular design while reducing footprint also reduces energy consumption Transition: HP delivers this capability with a cost-effective solution that includes wired, wireless, management, security, WAN optimization, application delivery, telephony, and UC&C capability that scales as business needs grow. … continuing on the theme of “complexity” being the enemy of - or standing in the way of “cloud” (ala Cisco) - vs. HPN FlexNetworking = simplicityperformance leadership on the HP 6600 routers and am highlighting the powerful multi-core distributed processing architecture - In fact, it take Cisco 5 boxes to reach performance I'm showing in one box (HP 6608). That amounts to 77% less rack space and 92% less power.Wan Routing and CLOUDIn terms of considerations - I think it can be broken down into 3 parts - High performance and Scale, Rich routing/QoS, security, switching capabilities, and carrier class high availability and fast convergence....Each aspect is extremely import - since you need to connect tens of thousands of users to a diverse set of applications across millions of flows - Without high scale and throughput routing and security services - you can not maintain exceptional application performance for cloud based applicationsRich features enables you to optimize application performance to ensure you are maintaining the same level of experience for cloud applications regardless of locationCarrier class availability and convergence enables you to recover extremely fast recovery and ensure un-interrupted application services (minimize any impact during network/device failures.)What are the implications of back-hauling all enterprise cloud traffic back to the data center (for security) – what are the performance, latency implications on the users? VDI design implications? E.g., a Citrix thin client can consume as much as 500Mbps of traffic … for a typical branch with a T-1 (1.5 Mbps) and 20+ users … how does a customer address this challenge?
  • 2/3rds of the worlds mobile traffic will be video by 2015 – immersive collaboration … pervasive videoSingTel LTE supports mobile Internet users speeds of up to 75 megabits per secondIs the users experience the same regardless of location, device, application????The need to identify and securely connect usersIT is facing a phenomenon called BYOD (bring your own device) that allows the use of personally owned laptops, smartphones and tablets by employees. Besides that, IT needs to give access to give internet access to the guest users and to apply a health check policy on devices used by employees and guest users to mitigate the risk to the business.Network Access Control solutions is the key component for BYOD ,guest users and health checkbecause it provides the flexibility that enterprises need in a BYOD environment, while providing the controls that enable network and security managers to keep control over the network.Gartner expects that, by 2016, 60% of large enterprises will implement limited access network zones to limit the connectivity of personally owned mobile devices and they estimate that the size of the NAC market in 2012 will reach $226 million.Device-dependentLegacy architectures rely on company-issued devices to deliver secure access to applicationsInconsistent managementSeparate management for wired and wireless devices are disaggregated, have separate policiesSeparate management for devices, applicationsLack of visibility into user behaviors, access, and usageSingTel will use the Long Term Evolution (LTE) technology, which allows mobile Internet users to experience speeds of up to 75 megabits per second, or over three times faster than current 3G technology using HSPA technology.This will also be the first time that the technology will be available to retail consumers. M1 had launched a similar service in June, but only for corporate customers.The offering marks another milestone in Singapore's adoption of the new telecommunications standard.Mr Yuen Kuan Moon, executive vice president of Digital Consumer with SingTel, said: "With higher bandwidth on mobile 4G services, we can now introduce a lot of new value added services that were previously only available on our fixed fibre network.
  • Application indifferent, topology dependant, manual managementLegacy networks are rigid and inflexible. Modern networks are programmable to meet a variety of needs. Finally, legacy networks require manual management using complex command-line interfaces (CLIs), or by juggling multiple management applications. With a modern network, you can manage different clouds—public, private and hybrid—using a common and simplified management platform.http://www.evolven.com/blog/downtime-outages-and-failures-understanding-their-true-costs.htmlLegacy networks are rigid and inflexible. Modern networks are programmable to meet a variety of needs. Finally, legacy networks require manual management using complex command-line interfaces (CLIs), or by juggling multiple management applications. With a modern network, you can manage different clouds—public, private and hybrid—using a common and simplified management platform.68% percent of organizations cite application reliability and performance as the most important factor for cloud computing. IDG Report, “Global Cloud Computing Adoption: Transformation is in the Air,” 2011"Through 2015, 80% of outages impacting mission-critical services will be caused by people and process issues, and more than 50% of those outages will be caused by change/configuration/release integration and hand-off issues." Gartner - Ronni J. Colville and George SpaffordConfiguration Management for Virtual and Cloud Infrastructures) Application indifferentForwarding packets in a void without context of the seemingly infinite and constantly changing set of applications and devices Rigid, physical networkArchitected for one tenant, one type of user, one type of location, one class of application and one SLA; lacking programmability and inhibiting scaleManual managementManaged device-by-device with either complex CLI and scripting or multiple management apps; set and forgotten
  • Let’s focus on the amount of time it takes to connect an application to the network. Let’s start with the tools that a server administrator uses. He uses tools that allow him to manage with policy. He has very sophisticated tools and when he needs to connect to the network, that’s where the delay comes in and it takes weeks. Just look at the questions that a network administrator asks the server admin. These are much lower level questions. Because he isn’t using advanced policy-based tools. He is using 40-year-old technology comprising command-line interface and scripts. As a matter of fact, in an interview with a CEO, he told his team, “If you’re using the CLIN scripts, you’ve already lost the battle for cloud. “ In a typical data center, according to Cindy Borovick from IDC, you could have 500 servers with all of them running a hypervisor, each carrying about 20 virtualized workloads. Well, there are 10,000 workloads with each one requiring, on an average, five network attributes and there are 50,000 network attributes that you have to configure on a port-by-port basis across dozens of switches—possibly 250,000 command line entries across those dozens of switches. Even if you have a really good IT organization, those network administrators are bound to make a mistake.  Talking to Joe Skorupa from Gartner and his comment was, even if they are really good, they might make one mistake out of a thousand, that’s is still 250 errors and you’ve got to go find them—that’s the real tough part. This process is not only slow, but it presents a reliability problem.
  • HP’s Virtual Application Networks are our vision for Software Defined Networks. Virtual Application Networks enable businesses to spend less time managing infrastructure and more on connecting users to applications.
  • Characterize the applications: Once applications are characterized, the network is able to dynamically marshal and verify the appropriate resources for applications according to their characteristics. One characteristic, for example, could be whether the application is rich media, like surveillance video, which would require higher bandwidth.  2. Virtualize the network: You benefit from virtualized networks because you no longer have to build and manage inflexible overlay networks to accommodate the need for wired, wireless and secure remote connectivity. You can orchestrate a virtual network for different use cases.  3. Orchestrate the network: This helps to improve your work-life because management functions are automated, which helps to speed applications delivery. You should be able be able to manage multiple cloud delivery platforms from a single point. For example, a virtualized network would enable you to control whether a particular application workload runs on a private or public cloud. No more management in piecemeal.By breaking free of the siloed, rigid “network-centric” provisioning model—to a more open “application centric and infrastructure independent model—government agencies will be better positioned to take full advantage of cloud.
  • Let’s focus on the amount of time it takes to connect an application to the network. Let’s start with the tools that a server administrator uses. He uses tools that allow him to manage with policy. He has very sophisticated tools and when he needs to connect to the network, that’s where the delay comes in and it takes weeks. Just look at the questions that a network administrator asks the server admin. These are much lower level questions. Because he isn’t using advanced policy-based tools. He is using 40-year-old technology comprising command-line interface and scripts. As a matter of fact, in an interview with a CEO, he told his team, “If you’re using the CLIN scripts, you’ve already lost the battle for cloud. “ In a typical data center, according to Cindy Borovick from IDC, you could have 500 servers with all of them running a hypervisor, each carrying about 20 virtualized workloads. Well, there are 10,000 workloads with each one requiring, on an average, five network attributes and there are 50,000 network attributes that you have to configure on a port-by-port basis across dozens of switches—possibly 250,000 command line entries across those dozens of switches. Even if you have a really good IT organization, those network administrators are bound to make a mistake.  Talking to Joe Skorupa from Gartner and his comment was, even if they are really good, they might make one mistake out of a thousand, that’s is still 250 errors and you’ve got to go find them—that’s the real tough part. This process is not only slow, but it presents a reliability problem.
  • Let’s go back to our original example of deploying an exchange instance and its virtual machines. Click #1: With Virtual Application Networks, the first step is to characterize the application delivery requirements for Exchange in the IMC VAN Manager Module. Click #2: Here, we build a connection profile from a preconfigured template. Click #3: The second step is to virtualize the server to network connectivity in VMware vCenter with a plug-in that comes with the IMC VAN Manager module. Click #4: Here, the sys admin simply chooses the connection profile for Exchange. Every time a new Exchange instance is deployed, the same profile is selected, ensuring speed, consistency and reliability. Click #5: The third step is to orchestrate the network with the IMC VAN Manager module where the Exchange VMs are visible after selecting the connection profile. Click #6: By simply “powering them on,” IMC will automatically configure the switches based on the connection profile. Click #7: The application is deployed in three easy steps! And I never had to touch the command line interface!
  • You understand our vision for virtual application networks. Well, this is how it all comes together. We start with the blueprint FlexNetwork architecture, with the solutions for the data center FlexFabric, FlexCampus and FlexBranch to connect the users. We are going to virtualize that entire infrastructure symbolized by these three blue ribbons that come into the center discs. And here, once we virtualize the network, we can use tools built on top of IMC to characterize applications using preconfigured templates. So that we can take advantage of virtualized, end-to-end network infrastructure to deliver applications from a cloud data center to a user in a way where the network is tuned to the delivery requirements of that class of applications whether it is video in multiple forms, conferencing, playback, training, or communications like Lync, real time business applications or messaging applications. You can have hundreds of applications falling into several classes requiring maybe 12 different virtual application networks. Most importantly, as these applications move from the private cloud into the public cloud, the policy for virtual application network can follow it as the users move and we will follow them as well providing for a dynamic environment, one where the applications are deployed rapidly. You can have speed without compromise and it is built on open standards, providing the choice, the flexibility as well as the confidence to have a proven path to the cloud.
  • Evolving enterprise networks to support cloud models The bottom line is that contemporary data center networks designed to support siloed IT architectures simply aren’t designed meet the performance, security, availability and agility requirements of cloud. As IT/network operators begin to think (or re-think) about how you will build and design you networks moving forward to accommodate emerging cloud use models, you would be well served to consider HP’s FlexNetwork Architecture. HP FlexNetwork Architecture: why it’s right for supporting cloud computing Our HP FlexNetwork Architecture allows enterprises to securely deploy and centrally orchestrate cloud-optimized architectures that scale from the data center to the network edge. HP FlexNetwork enables the construction of flatter, simpler data center networks to support the bandwidth-intensive, delay-sensitive server-to-server virtual machine and workload traffic flows that accompany cloud.The benefits of HP FlexNetwork Architecture include: Massive architectural design simplification, connecting users to applicationsHigh-performance, low-latency, ultra-resilient virtualized networking fabric Open standard-based networks designed to lower operational complexity and cost Learn more HP’s Building Cloud-Optimized Data Center Networks is a helpful resource if you are looking at how to best “cloud-optimize” your network to address the new generation of requirements that cloud demands. You might also want to watch these two videos:  >>The Future of the Cloud>> SHI Delivering Cloud Services by Changing the Rules of Networking with help from HP
  • The key take-away I want to convey is that customers can start taking steps TODAY to “cloud optimized” their networks in a very migratory manner in the DC, across the enterprise etc … (depending on where they are at with “cloud”) … while at the same time they are improving their overall IT environment an operating (cloud or no cloud). … - but by partnering with HP … we have the products and vision that can help get you to where you want to go. You can start today! Revisit existing network design assumptionsTake an “Application Centric” perspective - Lots of buzz in the DC - but don’t forget the rest of your networkTactical IT networking best practices can be made along the wayHP can help you design and build your “network”
  • From a networking standpoint, each service model requires thecloud provider to expose more or less of the network and providemore or fewer networking capabilities to cloud users. Conversely, each service model requires cloud users to understand and design more or less of the network to which they are exposed. The network is most exposed in the IaaS model and least in the SaaS model.The essential technological difference between the deploymentmodels is derived from the networking relationship between thecloud user and the cloud provider. In a private cloud, the user and provider are within the same trusted network boundary. In a public cloud, they are on different networks. In a hybrid cloud, a secured connection may exist between the user’s and provider’s networks, or the user’s network may extend into the provider’s cloud (or the reverse)Every cloud is some combination of a service and deploymentmodel. Regardless of the type of cloud, however, one fact remainstrue: no network means no cloud.… is a model in which IT resources and services are abstracted from the underlying infrastructure and provided on demand and at scale in a multi-tenant environment.
  • From a networking standpoint, each service model requires thecloud provider to expose more or less of the network and providemore or fewer networking capabilities to cloud users. Conversely, each service model requires cloud users to understand and design more or less of the network to which they are exposed. The network is most exposed in the IaaS model and least in the SaaS model.The essential technological difference between the deploymentmodels is derived from the networking relationship between thecloud user and the cloud provider. In a private cloud, the user and provider are within the same trusted network boundary. In a public cloud, they are on different networks. In a hybrid cloud, a secured connection may exist between the user’s and provider’s networks, or the user’s network may extend into the provider’s cloud (or the reverse)Every cloud is some combination of a service and deploymentmodel. Regardless of the type of cloud, however, one fact remainstrue: no network means no cloud.… is a model in which IT resources and services are abstracted from the underlying infrastructure and provided on demand and at scale in a multi-tenant environment.
  • Gartner Legacy IT app deployments … Eric A … SPAIT Annual spend $1.7 Trillion in the coming years … less than 10% will be on cloudTraditional IT still very importantHybrid delivery model will be the normal It’s about the right mix of Cloud and traditional IT…. traditional IT will be here for a very long time.Before you start your strategy and roadmap, you have to recognize what the end goal it. It is NOT for everything to move to ‘the cloud’. It’s really about right-sourcing. Some IT will stay in traditional physical and virtual environment – won’t make sense to move 100%Part will be ‘private’ – or dedicated cloud resources either in your data center or hosted for youThe last part will be public cloud – for IaaS or SaaS.
  • Intel – Gen 8 severs – 10G LOM … $350/port … laying the foundation for migration to 10 G network access
  • Evolving enterprise networks to support cloud models So what’s my point? The bottom line is that contemporary data center networks designed to support siloed IT architectures simply aren’t designed meet the performance, security, availability and agility requirements of cloud. As IT/network operators begin to think (or re-think) about how you will build and design you networks moving forward to accommodate emerging cloud use models, you would be well served to consider HP’s FlexNetwork Architecture. HP FlexNetwork Architecture: why it’s right for supporting cloud computing Our HP FlexNetwork Architecture allows enterprises to securely deploy and centrally orchestrate cloud-optimized architectures that scale from the data center to the network edge. HP FlexNetwork enables the construction of flatter, simpler data center networks to support the bandwidth-intensive, delay-sensitive server-to-server virtual machine and workload traffic flows that accompany cloud.The benefits of HP FlexNetwork Architecture include: Massive architectural design simplification, connecting users to applicationsHigh-performance, low-latency, ultra-resilient virtualized networking fabric Open standard-based networks designed to lower operational complexity and cost Learn more HP’s Building Cloud-Optimized Data Center Networks is a helpful resource if you are looking at how to best “cloud-optimize” your network to address the new generation of requirements that cloud demands. You might also want to watch these two videos:  >>The Future of the Cloud>> SHI Delivering Cloud Services by Changing the Rules of Networking with help from HP
  • Design limitations not optimized for emerging traffic patternsBW explosion, N/S to E/W, Hub Spoke to meshDesign limitations not optimized for emerging traffic patterns/volumeLimited network visibility/control/security (E-E, physical and virtual)Inconsistent user experience, application performance/availability Dislocation between Application/VM & Network provisioning modelsAdding more boxes/bandwidth doesn’t helpThe WAN …Big pipe – little pipe issueThe need for Intelligence at the (WAN) edgeUnpredictable traffic patterns (back-haul, any to any) Poor Application PerformanceOptimized Application PerformanceDeployment/management complexity
  • Application indifferent, topology dependant, manual managementLegacy networks are rigid and inflexible. Modern networks are programmable to meet a variety of needs. Finally, legacy networks require manual management using complex command-line interfaces (CLIs), or by juggling multiple management applications. With a modern network, you can manage different clouds—public, private and hybrid—using a common and simplified management platform.http://www.evolven.com/blog/downtime-outages-and-failures-understanding-their-true-costs.htmlLegacy networks are rigid and inflexible. Modern networks are programmable to meet a variety of needs. Finally, legacy networks require manual management using complex command-line interfaces (CLIs), or by juggling multiple management applications. With a modern network, you can manage different clouds—public, private and hybrid—using a common and simplified management platform.68% percent of organizations cite application reliability and performance as the most important factor for cloud computing. IDG Report, “Global Cloud Computing Adoption: Transformation is in the Air,” 2011"Through 2015, 80% of outages impacting mission-critical services will be caused by people and process issues, and more than 50% of those outages will be caused by change/configuration/release integration and hand-off issues." Gartner - Ronni J. Colville and George SpaffordConfiguration Management for Virtual and Cloud Infrastructures) Application indifferentForwarding packets in a void without context of the seemingly infinite and constantly changing set of applications and devices Rigid, physical networkArchitected for one tenant, one type of user, one type of location, one class of application and one SLA; lacking programmability and inhibiting scaleManual managementManaged device-by-device with either complex CLI and scripting or multiple management apps; set and forgotten
  • Evolving enterprise networks to support cloud models The bottom line is that contemporary data center networks designed to support siloed IT architectures simply aren’t designed meet the performance, security, availability and agility requirements of cloud. As IT/network operators begin to think (or re-think) about how you will build and design you networks moving forward to accommodate emerging cloud use models, you would be well served to consider HP’s FlexNetwork Architecture. HP FlexNetwork Architecture: why it’s right for supporting cloud computing Our HP FlexNetwork Architecture allows enterprises to securely deploy and centrally orchestrate cloud-optimized architectures that scale from the data center to the network edge. HP FlexNetwork enables the construction of flatter, simpler data center networks to support the bandwidth-intensive, delay-sensitive server-to-server virtual machine and workload traffic flows that accompany cloud.The benefits of HP FlexNetwork Architecture include: Massive architectural design simplification, connecting users to applicationsHigh-performance, low-latency, ultra-resilient virtualized networking fabric Open standard-based networks designed to lower operational complexity and cost Learn more HP’s Building Cloud-Optimized Data Center Networks is a helpful resource if you are looking at how to best “cloud-optimize” your network to address the new generation of requirements that cloud demands. You might also want to watch these two videos:  >>The Future of the Cloud>> SHI Delivering Cloud Services by Changing the Rules of Networking with help from HP
  • SHI International pioneering data center design for cloud services http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-3001ENW.pdfReducing network complexity, boosting performance with HP IRF technologyhttp://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-9402ENW.pdfHP Intelligent Management Center Enterprise Software Platform (Free Trial)http://h17007.www1.hp.com/us/en/products/network-management/IMC_ES_Platform/index.aspxThe Total Economic Impact of HP TippingPoint IPShttp://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-6398ENW.pdfHP Intelligent Management Center Solution Briefhttp://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-4496ENW.pdf
  • Design limitations not optimized for emerging traffic patternsBW explosion, N/S to E/W, Hub Spoke to meshDesign limitations not optimized for emerging traffic patterns/volumeLimited network visibility/control/security (E-E, physical and virtual)Inconsistent user experience, application performance/availability Dislocation between Application/VM & Network provisioning modelsAdding more boxes/bandwidth doesn’t helpThe WAN …Big pipe – little pipe issueThe need for Intelligence at the (WAN) edgeUnpredictable traffic patterns (back-haul, any to any) Poor Application PerformanceOptimized Application PerformanceDeployment/management complexity
  • Traditional rack server designs 16 rack servers with 1 fully loaded BladeSystem C7000 enclosure. The rackmount servers would need a pair of ToR switches and the C7000 enclosure would have 2 VC modules. You can run up to 8 10GbE cables out of each module, but most commonly each module has one stacking cable to the another module and one 10GbE uplink cable out of the enclosure to a distribution switch someplace. 100% of the traffic need to be routed to outside/upstream to L2/3 devices/layers – adding latency and poor user/application experience80% of the traffic stays “local” to the enclosure – delivering much lower latency and a superior user/application experienceHPVirtual Connect modules in the back of the enclosures, this allows us to also apply Insight Orchestration to enable pre-packaged automation, or apply the Virtual System reference models, or VDI.  The power savings were simply looking at the switch component of not having TOR and EOR and move to just end of room.  The power comparison was the number of CISCO switches used today compared against the HP approach of flattening the network with HP switches.  As well as the reduction in switches providing a reduction in power consumption we found during the analysis that some HP switches require less than half the power a CISCO switch requires. Don’t forget in terms of savings, we are have not included; air conditioning power savings, cabling cost reduction, support reduction, management FTE reduction, etc. So there is still lots of savings to be had even if the cost per KwH is reduced.  And the value was shared so that someone could come up with their won savings value based on the cost of electricity.
  • Application indifferent, topology dependant, manual managementLegacy networks are rigid and inflexible. Modern networks are programmable to meet a variety of needs. Finally, legacy networks require manual management using complex command-line interfaces (CLIs), or by juggling multiple management applications. With a modern network, you can manage different clouds—public, private and hybrid—using a common and simplified management platform.http://www.evolven.com/blog/downtime-outages-and-failures-understanding-their-true-costs.htmlLegacy networks are rigid and inflexible. Modern networks are programmable to meet a variety of needs. Finally, legacy networks require manual management using complex command-line interfaces (CLIs), or by juggling multiple management applications. With a modern network, you can manage different clouds—public, private and hybrid—using a common and simplified management platform.68% percent of organizations cite application reliability and performance as the most important factor for cloud computing. IDG Report, “Global Cloud Computing Adoption: Transformation is in the Air,” 2011"Through 2015, 80% of outages impacting mission-critical services will be caused by people and process issues, and more than 50% of those outages will be caused by change/configuration/release integration and hand-off issues." Gartner - Ronni J. Colville and George SpaffordConfiguration Management for Virtual and Cloud Infrastructures) Application indifferentForwarding packets in a void without context of the seemingly infinite and constantly changing set of applications and devices Rigid, physical networkArchitected for one tenant, one type of user, one type of location, one class of application and one SLA; lacking programmability and inhibiting scaleManual managementManaged device-by-device with either complex CLI and scripting or multiple management apps; set and forgotten
  • Let’s focus on the amount of time it takes to connect an application to the network. Let’s start with the tools that a server administrator uses. He uses tools that allow him to manage with policy. He has very sophisticated tools and when he needs to connect to the network, that’s where the delay comes in and it takes weeks. Just look at the questions that a network administrator asks the server admin. These are much lower level questions. Because he isn’t using advanced policy-based tools. He is using 40-year-old technology comprising command-line interface and scripts. As a matter of fact, in an interview with a CEO, he told his team, “If you’re using the CLIN scripts, you’ve already lost the battle for cloud. “ In a typical data center, according to Cindy Borovick from IDC, you could have 500 servers with all of them running a hypervisor, each carrying about 20 virtualized workloads. Well, there are 10,000 workloads with each one requiring, on an average, five network attributes and there are 50,000 network attributes that you have to configure on a port-by-port basis across dozens of switches—possibly 250,000 command line entries across those dozens of switches. Even if you have a really good IT organization, those network administrators are bound to make a mistake.  Talking to Joe Skorupa from Gartner and his comment was, even if they are really good, they might make one mistake out of a thousand, that’s is still 250 errors and you’ve got to go find them—that’s the real tough part. This process is not only slow, but it presents a reliability problem.
  • Characterize the applications: Once applications are characterized, the network is able to dynamically marshal and verify the appropriate resources for applications according to their characteristics. One characteristic, for example, could be whether the application is rich media, like surveillance video, which would require higher bandwidth.  2. Virtualize the network: You benefit from virtualized networks because you no longer have to build and manage inflexible overlay networks to accommodate the need for wired, wireless and secure remote connectivity. You can orchestrate a virtual network for different use cases.  3. Orchestrate the network: This helps to improve your work-life because management functions are automated, which helps to speed applications delivery. You should be able be able to manage multiple cloud delivery platforms from a single point. For example, a virtualized network would enable you to control whether a particular application workload runs on a private or public cloud. No more management in piecemeal.By breaking free of the siloed, rigid “network-centric” provisioning model—to a more open “application centric and infrastructure independent model—government agencies will be better positioned to take full advantage of cloud.
  • Let’s focus on the amount of time it takes to connect an application to the network. Let’s start with the tools that a server administrator uses. He uses tools that allow him to manage with policy. He has very sophisticated tools and when he needs to connect to the network, that’s where the delay comes in and it takes weeks. Just look at the questions that a network administrator asks the server admin. These are much lower level questions. Because he isn’t using advanced policy-based tools. He is using 40-year-old technology comprising command-line interface and scripts. As a matter of fact, in an interview with a CEO, he told his team, “If you’re using the CLIN scripts, you’ve already lost the battle for cloud. “ In a typical data center, according to Cindy Borovick from IDC, you could have 500 servers with all of them running a hypervisor, each carrying about 20 virtualized workloads. Well, there are 10,000 workloads with each one requiring, on an average, five network attributes and there are 50,000 network attributes that you have to configure on a port-by-port basis across dozens of switches—possibly 250,000 command line entries across those dozens of switches. Even if you have a really good IT organization, those network administrators are bound to make a mistake.  Talking to Joe Skorupa from Gartner and his comment was, even if they are really good, they might make one mistake out of a thousand, that’s is still 250 errors and you’ve got to go find them—that’s the real tough part. This process is not only slow, but it presents a reliability problem.
  • Let’s focus on the amount of time it takes to connect an application to the network. Let’s start with the tools that a server administrator uses. He uses tools that allow him to manage with policy. He has very sophisticated tools and when he needs to connect to the network, that’s where the delay comes in and it takes weeks. Just look at the questions that a network administrator asks the server admin. These are much lower level questions. Because he isn’t using advanced policy-based tools. He is using 40-year-old technology comprising command-line interface and scripts. As a matter of fact, in an interview with a CEO, he told his team, “If you’re using the CLI scripts, you’ve already lost the battle for cloud. “ In a typical data center, according to Cindy Borovick from IDC, you could have 500 servers with all of them running a hypervisor, each carrying about 20 virtualized workloads. Well, there are 10,000 workloads with each one requiring, on an average, five network attributes and there are 50,000 network attributes that you have to configure on a port-by-port basis across dozens of switches—possibly 250,000 command line entries across those dozens of switches. Even if you have a really good IT organization, those network administrators are bound to make a mistake.  Talking to Joe Skorupa from Gartner and his comment was, even if they are really good, they might make one mistake out of a thousand, that’s is still 250 errors and you’ve got to go find them—that’s the real tough part. This process is not only slow, but it presents a reliability problem.

Bb2373 gray _virtualize_you_dc_with_flex_fabric_final Bb2373 gray _virtualize_you_dc_with_flex_fabric_final Presentation Transcript

  • BB2373 – HP Networking Track:Virtualize your Data Center with HP FlexFabric© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • BB2373 – HP Networking Track:Virtualize Your Data Centerwith HP FlexFabricJohn GrayJune 2012© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Agenda  Mega market trends  Legacy network limitations  “Application centric” networking  Improving the operating model  Call to action3 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Mega Trends and Network ImplicationsUp to Up to At least Up to70% 10X 50 billion 3 monthsworkloads will be increase in network devices will connect to deploy newvirtualized by the end capacity, new wave of to wireless networks applications acrossof 2016 business video apps by the year 2020 the networkChanging traffic Bandwidth Consumerization of it Provisioning patterns explosion complexity4 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Legacy Network Limitations • Architectural limitations not optimized for emerging traffic patterns, volume, scale • Inconsistent user experience resulting in poor performance across LAN and WAN • Limited network control inhibits visibility and security • Dislocation between application, VMs, and network5 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to provisioning models (TTS) change without notice.
  • Application Centric NetworkingDelivering applications to users Data center campus Branches Remote/mobile6 users © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Virtualization’s Impact in the Data Center“… traffic flow between servers will increase by an order of magnitude. Thesenew traffic patterns will appear arbitrary and even chaotic, with fluctuations thatcan be 90-times higher than the traffic peaks experienced by most datacenters today.”7 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Flatter, Simpler Data Center Fabric ImprovesPerformanceVirtualization-optimized design Platform and network virtualization Increase performance Lower latency Higher availability Blade servers VM Agility Lower TCO Rack servers Rack servers Blade servers Legacy Architecture8 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • From Complex to Simple Benefits … 1.2x increase in compute capacity 22x increase in storage capacity 18x reduction in uplinks 5.1x reduction in access ports 9.7x reduction in cables $5.5M in Capex, $16.3M energy savings/year Space, power, coolingLess complexity, cabling, cost - more performance, compute, storage, agility …9 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Optimizing for Cloud in the Data CenterHigh performance, low latency, highly resilient networking fabric • 10, 40 Gigabit Ethernet • Resilient, non-blocking design • Fabric, I/O convergence • Workload mobility Data center • Physical & virtual visibility Design to accommodate an increasingly virtualized environment10 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Ensuring Delivery of Cloud Across the WANHigh performance WAN routing services • WAN scaling, performance • Rich WAN routing services • High availability, failure recovery • Flexible WAN connectivity • Unified management, security WAN, Internet Services Designed to accommodate the explosion rich media/video, bandwidth11 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Ensuring Delivery of Cloud in the CampusSimplicity, scale, high performance, low latency and resiliency • Converged wired & wireless • BYOD flexibility • Rich media “ready” • Unified management, security Campus Designed to accommodate unified secure access from any device, BYOD12 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Ensuring Delivery of Cloud in the BranchLAN - like experience across the distributed enterprise Branch • Converged network services • Optimized app delivery • Availability, survivability • Unified management, security Designed to optimized user experience regardless of WAN bandwidth13 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Ensuring Delivery of Cloud for Mobile UsersAnywhere, device-agnostic, secure, high performance access Remote/mobile users • Secure access for users/devices • Unified wired / wireless • Optimized application delivery • Centralized, policy-based access Design to accommodate an increasingly mobile, dynamic user population14 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Cloud Network Provisioning Limitations 3 months to deploy a new application from data center to user 70% of downtime is caused by mis- configuration 68% of organizations cite application reliability/performance as the #1 factor for cloud computingOperational silos … coupled with circa 1980 network provisioning model15 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Operational Silos Server team’s point of reference Network team’s point of reference16 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Circa 1980 Network Provisioning Model (CLI)Limiting scale, time to service, and business continuity17 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Legacy Networks Slow Application Deployment System Admin Deploying Rack 3 VLAN Subnet 10M CIR Priority Are you ready Exchange IP TOS Server 5 10 .16.31 20M PIR 4 yet? …VMs ready! Time in Months … Which 250,000+ Which Which How much QoS QoS Ok, starting CLI entries VLAN server? subnets? bandwidth? Priority? Method? switch config for typical ? data centerNetwork Admin (Layer 2-4)18 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • HP’s Vision for Software Defined NetworksHP Virtual Application Network Focus less on managing infrastructure… …and more on connecting users to applications19 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Creating Virtual Application NetworksTunes the Virtual Network for application delivery requirements Virtual Application Networks • Characterize applications • Virtualize the network • Automate orchestration20 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Legacy Networks Slow Application Deployment System Admin Deploying Rack 3 VLAN Subnet 10M CIR Priority Are you ready Exchange IP TOS Server 5 10 .16.31 20M PIR 4 yet? …VMs ready! Time in Months … Which 250,000+ Which Which How much QoS QoS Ok, starting CLI entries VLAN server? subnets? bandwidth? Priority? Method? switch config for typical ? data centerNetwork Admin (Layer 2-4)21 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Virtual Application Networks Deploy Apps in Minutes VirtualizeSystem Admin Deploying vCenter Virtualizing Wow! Faster time to service Exchange That was 10-100x Plug-in VMs … ready! fast! 2 Application Application-centric deployment Minutes deployed 1 Characteriz 3 Orchestrat in 3 steps Simplified, template e e IMC IMC driven, repeatable VAN VAN Manager VM Manager s cloud provision modelNetwork Admin 22 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Deploy Cloud Applications in Minutes, notMonthsAutomating policy-based configuration from application-to-network-to-user23 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Cloud Networking Take-a-ways Start today! Revisit existing network design assumptions Take an “application centric” end-to-end perspective - Lots of buzz in the DC - but don’t forget the rest of your network/users Significant network/IT improvements can be made along the way HP can help!!! (design and build, tailored solutions and services)24 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Tools to Help Our Clients• Read more on FlexFabric• Read about the FlexNetwork Architecture• Learn about Virtual Application Networks• Discover Intelligent Management Center• View the HPN Portfolio Matrix Guide• Learn about networking services from HP Technical Services• Learn about networking career certifications from HP ExpertONE25 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Find out more Attend these sessions Visit these demos After the event • RT2388 • HE: HP FlexNetwork • Contact your sales Forging the way to Architecture representative the Cloud • HJ: HP Virtual • Visit the Application Networks www.hp.com/networking • HG: Intelligent Management Center (IMC) Your feedback is important to us. Please take a few minutes to complete the session survey.26 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • Thank you© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.