EVA Upgrade

This post covers the upgrade process for a EVA Upgrade.  I wrote it ages ago but never got round to publishing it.  In the spirit of blogtober I wanted to get it out there as I am sure there are still some HP EVA’s in use .

This is the steps I followed to upgrade the firmware on an EVA. You can read further on the steps using the EVA upgrade guide

Week Before

  • Check current EVA and Command View versions
  • Upgrade Command View to compatible version if relevant -10.3
  • Download firmware from software depot
  • Check for any hardware failures
  • Upgrade HBA and switch firmware – check compatibility with SPOCK
  • Check disk grouping policy is set to manual. System options, configuration, set system operation policies, manual
  • Ensure you have The EVA SSSU (HP Storage System Scripting Utility) the command line tool for managing EVA systems installed. SSSU will generally be installed on your EVA management server
  • To Use EVA SSU launch the program from the shortcut. You will then see a screen like belowSSSU for HP P6000 Command View

    Version: 10.2.0

    Build: 091012A

    Manager:Name or IP address of CommandView Server

    Username:administrator

    Password:

    Under manager enter the IP address or hostname of you EVA management server, then log on with an account with rights to the system. You can check which accounts have rights by looking at the local security group xxxx on the management server and seeing what local accounts are in there.

    Once logged in you will need to choose which system to manage. To see what systems are available first list them:

    NoSystemSelected> ls system

    Systems available on this Manager:

    EVA01

    Then select which system you want to manage.

    select system EVA01

Day Before

  • Check hardware
  • Check events – controller events
  • Backup EVA system config as follows:

First connect and logon to the system using EVA SSSU instructions as described above

To capture system config to a file:

capture configuration C:config.txt

You can use the capture validate command to verify if the contents of the file still match the current configuration of the EVA.

Capture validate <filename to check>

 Also as a best practice run ls disk_group full, ls host full, ls vdisk full before an upgrade

ls disk_group full > C:disk.txt

ls host full C:host.txt

ls vdisk C:vdisk.txt

  • Backup data on EVA

Day of Upgrade

  • Check hardware and controller events
  • Configure User-Initiated Service Mode (UISM). System options, configuration, configure User-Initiated Service Mode (UISM)
  • Disabling array passwords. Settings, management options, security options – manage storage system password access
  • Shut down hosts – if offline
  • Upgrade controller software – system options, code load system
    • Tick box confirming you have completes pre-upgrade checks
    • System runs automated system checks to see if its fit to continue
    • Code transferred to controllers
    • Upgrade begins
    • Nodes reboot
  • Verify version of XCS firmware after upgrade
  • 30 min after upgrade check IO module firmware on disk enclosure
  • Upgrade drive firmware allow 30sec-3 min per drive

The Machine – Does It Change Everything?

During HP Discover last month Meg Whitman said of The Machine “This changes everything”, so what is The Machine and does it change everything?

 

What is MoonShot?

Let’s start by talking about HP MoonShot, this is not The Machine nor does it use the unique architecture we wil learn The Machine uses, however it is in production and has been based around some of the concepts that The Machine will harness. A MoonShot system is housed in a 4.3 U chassis and can accommodate 45 servers, or in MoonShot speak server cartridges. So this is some kind of an ultra compact BladeCentre replacement, right? Wrong,  since each server cartridge is not as powerful as a traditional blade server. Where HP MoonShot shows its teeth is with workloads that require massive parallel processing such as real time data processing. The photo below shows an example of one of the server cartridges sitting on top of the system

 

1 MoonShot

New Efficiencies

MoonShot is a hyper-scale computing platform, but as well as that its other USP is its efficiency. The need to develop a more energy efficient computing platform was based on the premise that the current approach to computing is not sustainable in terms of power and space requirements. HP quote the Moonshot as using 65% less power, 90% less space and 98% lass cabling than traditional computing.

 

 Software Defined Server

When the MoonShot server first came out HP talked about it being a software defined solution, but now that terminology has been used extensively for another meaning it appears to have been dropped from HP’s literature. But what they meant when they said software defined was that the cartridge you chose would be defined by the application requirements i.e. different workloads would benefit from different server cartridges.

 

The Machine

The Machine project is seen as being as so important by HP that it is investing two thirds of its R&D money in it, so this is almost an all or nothing bet. The name The Machine came about because HP is designing a new computing architecture that it sees as being applicable to all situations from your phone right up to hyper-scale computing.

Need for the Machine

HP started developing The Machine to contend with the exploding digital universe and a predicted 30 billion connected devices by 2020. This level of exponential growth was seen as unsustainable with current architectures and demanded a new approach to computing.

MoonShot First

As discussed earlier HP sees Moonshot as a close relation to the machine project, in that its goals are similar to enable efficient computing for tomorrow’s ever growing demand. Where The Machine differs from MoonShot and every other computer out there today is that it is based on a completely new computing archituure. The existing computing architecture The Von Neumann model has existed since 1945 and changed little in that time.

The Machine Architecture

The Machines unique architecture is based around three key elements:

Special purpose cores – This means customised hardware for specific use cases. MoonShot is already using specialised cores for different workloads, check out this Moonshot product guide which gives an idea of how different cartridges exist for different work loads.

Photonics – Instead of using copper wires between components, fibre cables with light are used to bring a big boost in speed. This technology also allows multiple servers to be combined together using the high speed interconnects.

Universal memory – This is one of the key enhancements and creates one universal area of memory which does away with the separation of memory and disk. This universal memory area is as fast as RAM whilst allowing data to be stored permanently. HP are calling this unified memory area memristors.

Closeup of HP's Memristor devices on a 300mm wafer.

How the elements fit together can be seen in the diagram below. One of the aims of The Machine was to flatten the data hierarchy.  Storage and memory become one with universal memory, then high speed communications between special purpose cores and universal memory is enabled via photonics.

 

All of these innovations HP claim allows the machine to be five times more powerful at 80% less power versus traditional computers. Such a radically new architecture needs a new OS so HP is designing its own OS from the ground up. Check out this video for more information The Machine at HP Discover

Does The Machine Change Everything?

The capabilities of the hardware on paper certainly seem like a game changer and it makes sense that a new architecture is required given the changes that have occurred since the The Von Neumann model was conceived. Given the amount of money that HP is ploughing into this and that it is effectively staking its reputation on it, you would have to bet that they will go on and deliver the hardware.  But I think the main challenge they will face is inertia.

What will push manufactures to want to put this new technology in their new phone, car etc. for what will inevitably at least initially be a higher price point.  Couple this with the challenge of developing an OS from the ground up and developing applications around it when most OS’s have decades of development around them and you can see the initial challenge faced by HP will be vast.

History has also shown that the best technology often doesn’t become the most successful, such as in the classic video recorder standard battle where VHS went on to become the dominant platform even though it was technically inferior to Betamax. Another lesson from history is that the innovator doesn’t always go on to become the dominant market player.  For example during the 70’s Xerox invented much of the modern computing world we see today – Ethernet networking, laser printers, and the PC but considering the scale of the innovations didn’t go on to be a dominant market force in any of these areas.

I think the need for a new computing platform given the exploding digital universe is a given, HP attempting to be the company that takes us there is a bold and confidant move.  Is it the right decision, ask me again in 10 years.

Follow 3ParDude on Twitter