Archive

Archive for the ‘HP’ Category

HP FlexNetwork Architecture poster – Deployment Scenarios #hp_networking #HPConverge #HPFlexNetwork

March 30, 2013 Comments off

Download the poster here: http://bit.ly/X3ZLn3

HP FlexNetwork Architecture Poster

Advertisements

HP Networking Product Portfolio Guide #hp_networking #HPConverge #HPFlexNetwork

March 30, 2013 Comments off

Download the HP FlexNetwork Portolio Guide here: http://bit.ly/16oebkL

HP FlexNetwork Porfolio Guide

HP Networking Product Portfolio Poster #hp_networking #HPConverge #HPFlexNetwork

March 30, 2013 Comments off

Download the Poster as PDF here: http://bit.ly/10j9tRq

HP Networking Product Portfolio Poster

HP FlexNetwork Porfolio Guide2

HP Converged Infrastructure Reference Architecture Design Guide – Accelerating IT with HP Converged Infrastructure #HPConverge

March 29, 2013 Comments off

The  technical white paper can be downloaded here:  http://bit.ly/YJ00o0

Courtesty of HP Converged Infrastructure

2

3

4

5

6

7

HP #FlexFabric Reference Architecture – Applying HP Converged Infrastructure to data center networks #HPConverge

March 29, 2013 Comments off

HP FlexFabric Reference Architecture – Applying HP Converged Infrastructure to data center networks

The  technical white paper can be downloaded hereL http://bit.ly/ZsXvlK

Courtesty of HP Converged Infrastructure

 

HP ConvergedNetwork WhitePaper

HP ConvergedNetwork WhitePaper TOC

Overview of the Guide

This guide is intended for technology decision-makers, solution architects, and other experts tasked with improving data center networking. It can serve as a baseline for network planning and design projects.

It is said, “You cannot chart your course without first knowing whence you came.” This also applies to data center architecture. However, many technical guides take the opposite approach. They attempt to sway the reader towards specific technical directions based on the merits of a current technology or standard. That approach often loses the reader because it does not provide a context for why the new technical approach was developed in the first place.

This document will frequently reference technology trends in the data center which have and are being driven through virtualization and standards. It will also introduce issues that confront data center architects in this fast-paced, results-driven, and security-minded industry.

Technical documents often promote a vendor’s products or vision. This document takes a slightly different approach. Rather than put HP’s vision for converged network infrastructure first, this guide instead presents the building blocks for that vision. It does this by first identifying the most important IT trend today—virtualization of resources at all levels. It then moves forward by introducing HP-supported technologies that enhance virtualized computer networks. Finally, it provides FlexFabric Reference Architecture examples for different types of virtualized server deployments using a layered approach.

The FlexFabric Reference Architecture guide is less of a discussion on specific HP equipment, and more of an overall focus on two things—virtualization and HP Networking technologies that support virtualization. It provides another level of detail to complement the HP Converged Infrastructure Reference Architecture Solution Block Design Guide http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-6453ENW.pdf

HP believes simplification is the overriding key to success in networks supporting virtualization. This document provides guidance on network simplification for virtualized deployments that do not sacrifice performance or deployment flexibility.

The major concept areas that will be covered are:

  • Virtual server networking
  • Securing the virtual edge
  • Managing the virtual edge
  • Converged network infrastructure

This approach allows data center architects and IT teams to develop new and more flexible data center models and methodologies. By doing so, IT can meet new demands head-on, rather than forcing businesses to adapt to technology limitations.

…Converged network infrastructure: unifying data and storage networks

Convergence is a technical term historically used to express the combining of voice and data onto the same network fabric. Now expressed as a converged network infrastructure, it encompasses the sharing of network resources between data and storage networks. This trend constitutes a move towards a unification of data and storage networks.

Network technologies like Fibre Channel, used to connect storage resources to computers, differ substantially from network technologies used to connect computer networks. Although high in performance, these network types create two dissimilar data center networks (LAN/WAN and storage), which increase the number of cables and management.

Technologies such as blade servers have addressed this challenge by drastically reducing the number of interconnections. Blade servers have simplified the network by reducing cables and Ethernet ports by over 75 percent. Converged network infrastructure can reduce data center complexity by an additional 50 percent, using technologies like Fibre Channel over Ethernet (FCoE), and more efficient technologies like data center bridging (DCB), also known as converged enhanced Ethernet (CEE).

ConvergedInfra

All of these emerging network technologies have an effect on how data centers are being planned for the future, but it is also important to understand how these technologies evolved.

The remainder of this section focuses on identifying what is currently used in data center network deployments, as well as identifying HP’s vision of converged network infrastructure….

Everything you wanted to know about HP #BladeSystem [#CloudSystem] #Matrix #MOE

March 29, 2013 Comments off

Everything you wanted to know about HP BladeSystem Matrix  Operating Environment (MOE) (now CloudSystem Matrix)

An extract from an older topic from 2011 on HP BladeSystem, but contains some useful historical / background information.

Courtesy of virtualizetips.com  Full oiginal article here: http://bit.ly/11VTDBp

With all the talk about converged infrastructure and stacks these days especially in the virtualization space I was really glad that I got to do this interview. There has been a lot written about its competitors but the HP BladeSystem Matrix was still kind of a mystery to anyone that had not had HP in to talk about it. I was lucky enough to spend some time talking with a couple of members from the HP BladeSystem Matrix team. These guys were very helpful in explaining what Matrix is and answered all of my crazy questions.

What I hope everyone gets from this is a better understanding of what BladeSystem Matrix has to offer if you’re looking at these types of converged offerings. Also highlight some of the features that are unique to the HP stack. In interest of being totally open I am also an employee of HP but my current work responsibilities have nothing to do with BladeSystem Matrix. Now that all that is out of the way let’s get started with the good stuff.

VT: Can you give me your elevator pitch? HP: Matrix is the foundation for a private cloud solution managing both physical and virtual infrastructure. Matrix allows you to rapidly provision infrastructure via a self service portal. In addition, it offers the ongoing life-cycle management including capacity planning and disaster recovery. You can buy Matrix with a single SKU that includes hardware, software and services. The solution is all tested and certified by HP to work together.

VT: Who benefits from this solution? HP: Customers who need to be able to address fast change and achieve a competitive advantage through time to market. Typical customers for Matrix are large Enterprises and Service Providers who have invested already in virtualization and shared infrastructure and want to take the next step to cloud computing. I think that these target customers are common to all converged infrastructure offerings.

VT: What hardware makes up a BladeSystem Matrix? HP: BladeSystem Matrix all begins with something called a starter kit. This kit includes the following items, Central Management Server on a ProLiant DL360, HP C7000 Blade Chassis w/Virtual Connect networking and Insight Management software for managing Matrix. For the storage you have multiple options – you can use your existing Fiber Channel SAN storage if it’s supported or you can use HP storage, e.g. 3PAR or HP EVA 4400 array. iSCSI storage is supported as well for VM data stores. There is also something called an Expansion kit which is a C7000 Blade chassis, Insight Management software licenses and HP Services needed to integrate the expansion kit into your existing Matrix environment. It should be noted that Matrix supports both ProLiant and Integrity blades.

VT: What are HP Cloud Maps and how do they relate to BladeSystem Matrix? HP: These Cloud Maps help customers to get started quickly with Matrix – they jump start the creation of a customized self-service portal.  Cloud Maps include white papers and templates for hardware or software configurations that can be imported into BladeSystem Matrix that can save days or weeks of design time. A Cloud Map can also provide workflows and scripts designed to expedite the installation.

VT: What does the CMS or Central Management Server do? HP: The CMS server is a physical server that is running the management software that controls, automates and monitors your BladeSystem Matrix. If you have a DR site with a Matrix you would need a CMS server there to control the environment. It’s also possible to setup the CMS in a HA or Highly Available configuration to prevent a single failure point for Matrix management. Lastly for large environments that exceed the maximums of a single CMS you can now stand up secondary CMS servers that will still allow you to manage everything from one admin console.

VT: Can I use existing HP gear with a Matrix install? HP: If you purchase a new HP BladeSystem Matrix you can use it to also manage any qualifying HP hardware that you already own. HP has created something called the Matrix Conversion Services to assist with integrating your existing HP infrastructure with BladeSystem Matrix. This program is new and will evolve to allow customers to accomplish these integrations.

VT: Can I use arrays from other vendors? HP: You can use Storage Arrays from other vendors as long as they are able to meet a list of criteria – for example the storage vendor needs to be certified with Virtual Connect.  More details can be found in the Matrix compatibility chart.

VT: What software is used for Matrix? HP: The software for Matrix is called the Matrix Operating Environment, which includes the whole Insight Management stack including Insight Foundation and Insight Control. With Insight Foundation you get the controls to install, configure, and monitor physical servers. With Insight Control you get all the essential server management including server deployment and power management. The real magic happens with the additional Matrix Operating Environment software (aka Insight Dynamics). It provides a service design tool, infrastructure provisioning with a self-service portal, capacity planning, and recovery management

VT: What types of automation and provisioning can Matrix do? HP: One example would be in the creation of templates. You can create templates in the Matrix software or use ones already created, for example on your VMware vCenter server. If you use an existing template that might be created with only one OS partition you can use the Matrix template process to provision the VM and add on additional disks and features not present in the base template.

VT: How does it integrate with VMware? HP: The HP tool set for BladeSystem Matrix offers many integration points with VMware vSphere. A short list of the functions would include provisioning VM’s, change in power state, activate/deactivate, add servers to group, and add disks to a VM or group of VM’s. Along with those features Matrix monitors status and performance, capacity & workload analysis and Disaster Recovery integration.

VT: What separates Matrix from other converged stacks? HP: A big selling point is that HP BladeSystem Matrix is integrated and engineered holistically by one company, while still allowing for heterogeneous components in areas such as networking and storage. Also at this time BladeSystem Matrix is the only solution that is capable of managing both physical and virtual servers with the same tools and allow movement between physical and virtual resources. Something that Matrix offers that others do not is integrated automated Disaster Recovery. Lastly Matrix supports both VMware and Microsoft Hyper-V, as well as Integrity Blades, for virtualization.

VT: What SAN protocols are supported today? HP: As of today BladeSystem Matrix supports Fiber Channel as the preferred method of connecting to storage. In addition, Matrix does support FCOE and iSCSI for VM data stores.

%d bloggers like this: