vPars & Integrity VM v6.1 comparison - HP Discover Online 2012 ...

HP-UX vPars & Integrity VM v6.1 

Dave Olker / June 2012 

© Copyright 2012 Hewlett-Packard Development Company, L.P. 

The information contained herein is subject to change without notice.

HP-UX vPars & 

Integrity VM v6.1 

Technology Overview 

Dave Olker / June 2012 



Agenda 

1. Overview 

3 

• New features 

• Performance Improvements 

2. vPars/VM feature comparison 

3. Performance characterization 

4. Summary and futures 

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

vPars & Integrity VM v6.1 

New features 



vPars & Integrity VM v6.1 new features 

5 

vPars & VM 

Offline VM/vPars 

transformation 

Superdome2 & 

rx2800 i2 support 

Perf improvements 

Direct I/O networking 

Large receive offload 

vPars v6.1 

Offline migration 

Perf improvements 

Redesigned AVIO 

Network & storage 

implementation 

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 

VM v6.1 

Legacy DSF and VIO obsolescence 

• NPIV & GUID Manager 

Integration 

• Pre-Tukwila server 

support

Offline vPars/VM v6.1 Transformation 

6 

• Easily convert v6.1 vPars to VMs or vice versa 

• CPU entitlement implications 

– VM � vPar = CPUs become dedicated to the vPar 

– vPar � VM = VM vCPUs entitlements default to 100% 

• Transformation caveats 

– A v6.1 VSP can run either VMs or vPars – not both simultaneously 

– Transformation is not supported on pre-Tukwila servers 

– NIC instance numbers can change during conversion (Portable Image helps) 

PI instructions: Integrity BL860c i2, BL870c i2 & BL890c i2 Server Blade User Service Guide 


VSP: Virtualization Services Platform 

(aka VM Host, Hypervisor) 

vPar VM

VM to vPar Transformation example 

7 

VSP> hpvmstatus -s | grep supported 

vPar/VM types supported by this VSP = Shared 

VSP> hpvmstop –p2 

VSP> hpvmstatus 

[Virtual Machines] 

Virtual Machine Name VM # Type OS Type State #VCPUs #Devs #Nets Memory 

==================== ===== ==== ======= ========= ====== ===== ===== ======= 

atcuxvm2 1 SH HPUX Off 8 4 1 64 GB 

atcuxvm5 2 SH HPUX Off 8 4 2 64 GB 


vPar/VM types supported by this VSP = vPar, Shared 

VSP> hpvmmodify -p2 -x vm_type=vpar 

VSP> hpvmstart –p2 


vPar/VM types supported by this VSP = vPar 

Convert VM to vPar 

and start vPar 


VSP is in VM mode 

(i.e. Shared guests) 

All VM guests stopped 

VSP can run either 

vPars or VMs 

VSP is in vPar mode

Offline vPars v6.1 Migration 

Move vPars between different physical servers 

• Distinguishing feature 

from previous versions 

of vPars! 

• Evacuate a VSP server for 

upgrades, repairs, etc. 

• Rebalance VSP resources 

8 


HP-UX 

vPar2 

HP-UX 

vPar1

N-Port ID Virtualization (NPIV) 

Direct storage visibility for vPars and VMs 

• Virtual FC ports share a Physical FC port 

• Improved storage security 

• Provision storage directly to the vPar or VM 

• VSP doesn’t see storage provisioned to vPar or VM 

• Enables enhanced storage features 

• Applications requiring physical disk/array access 

• 11i v3 Native Multi-Pathing inside the vPar or VM 

9 


vm1 

NPIV 

WWN1 

LUN1 

VSP 

Physical 

FC Port 

LUN2 

vm2 

NPIV 

WWN2

NPIV Supported Limits for vPars & Integrity VM v6.1 

10 

Description Limit 

NPIV HBAs per vPar/VM 8 

NPIV HBAs per Physical FC Port 16 

LUN Paths per NPIV HBA 2048 

Paths per NPIV LUN (Multipath) 8 

LUNs per NPIV HBA 2048 

NPIV LUNs per vPar/VM 2048 

LUN Paths per vPar/VM 16384 


NPIV Notes 

• NPIV is now available for 

Integrity VM v4.3 w/ PK2! 

• Only 11i v3 VMs support NPIV 

• Install latest AVIO Storage 

drivers for NPIV fixes 

• NPIV is supported on QLogic 

cards only. Emulex support is 

planned for a future OE.

Globally Unique Identifier (GUID) Manager 

Repository to allocate and manage unique World Wide Names for NPIV HBAs 

Goals 

11 

• Avoid configuring 

VMs and vPars with 

duplicate NPIV WWNs 

• Reduce risk of data 

corruption 


Globally Unique Identifier (GUID) Manager 

Recommended but optional service to manage NPIV WWNs 

• Client/Server PostgreSQL Database 

• GUIDMgr Server: Not recommended for installation on the VSP 

• GUIDMgr Client: Install on the VSP 

• GUIDMgr Server runs on nearly any HP-UX 11i v3 system 

• Unique Organizational Unique Identifier (OUI) 

• Avoids conflicts with physical FC WWNs or other WWN repositories 

• 0x50014c2 (first 7 digits of the WWN) 

12 


GUID Manager Integration with vPars & Integrity VM 

Several vPars and VM commands are GUID Manager “aware” 

13 

– hpvmcreate(1M), vparcreate(1M) 

– hpvmmodify(1M), vparmodify(1M) 

– hpvmremove(1M), vparremove(1M) 

Example: request WWNs from the GUID Manager and assign them to vHBAs 

# vparcreate -p atcuxvm5 -a hba:avio_stor:,,,:npiv:/dev/fcd0 

# vparmodify -p atcuxvm5 -a hba:avio_stor:,,,:npiv:/dev/fcd1 

# vparstatus -v atcuxvm5 

[IO Details] 

network:avio_lan:0,0,0x12b0a7b3f5bc:vswitch:vsw-15:portid:1 

hba:avio_stor:0,5,0x50014C2000000000,0x50014C2800000000:npiv:/dev/fcd0 

hba:avio_stor:0,6,0x50014C2000000001,0x50014C2800000001:npiv:/dev/fcd1 


Expanded Integrity Server Support 

14 

SD2 and rx2800 i2 support 

added for vPars & VM v6.1 


© The Copyright information 2012 contained Hewlett-Packard herein is Development subject to change Company, without L.P. notice. 

The information contained herein is subject to change without notice. 

Pre-Tukwila server support 

added for Integrity VM v6.1


Performance improvements 



vPars & Integrity VM v6.1 performance improvements 

16 

VM v6.1 

• Direct I/O Networking 

• Large Receive Offload 


vPars v6.1 

• Direct I/O Networking 

• Large Receive Offload 

• Redesigned AVIO 

Networking & Storage 

Implementation

Direct I/O Networking 

Directly assign a network device or individual NIC port to a vPar or VM 

• Significantly improves throughput and reduces CPU utilization 

− vPars: Near-native network I/O performance and CPU utilization 

− VMs: Improved network throughput, reduced CPU utilization on the VSP 

• Direct I/O NICs and AVIO NICs coexist in the same vPar or VM 

• Migration implications 

17 

− Offline migration of vPars or VMs using Direct I/O devices is supported 

− Online migration of VMs using Direct I/O devices is not supported 


Direct I/O – Device Level Assignment 

• All functions 

(including VC 

FlexNIC ports) 

assigned to the 

same VM or vPar 

• Broadcom NICs 

(including LOMs) 

support DLA only 

18 


Direct I/O – Function Level Assignment 

• Individual NIC ports 

(or VC FlexNIC ports) 

may be assigned to 

different VMs or 

vPars, or the VSP 

• Emulex NICs 

support Function 

Level Assignment 

19 


Large Receive Offload (LRO) 

Large Receive Offload support added to Host AVIO LAN driver 

• Receive-side equivalent of 

TCP Segmentation Offload 

• Aggregates incoming 

packets from a single 

stream into a larger buffer 

• Reduces CPU overhead 

20 


# nwmgr -A all -c lan22 

lan22 current values: 

Link State = Up 

Speed = 10000 Mbps Full Duplex 

MTU = 1500 

Receive Flow Control = On 

Transmit Flow Control = On 

Transmit CKO = On 

Receive CKO = On 

Virtual MTU = 32160 

Receive Interrupt Coal = 32 

Transmit Interrupt Coal = 32 

TCP Packet Reassembly in Driver = On 

Receive Queue Count = 5

vPars Redesigned AVIO Networking & Storage 

• Significantly better I/O performance vs. AVIO in a VM 

• Both storage (AVIO and NPIV) and networking benefit 

• Significant reduction of CPU utilization for I/O processing 

• Streamlined I/O and optimized interrupt processing 

21 

Bottom Line: Both vPars and VMs can use AVIO, 

but AVIO performs significantly 

better inside a vPar 



Feature comparison 



vPars & Integrity VM v6.1 comparison (part 1) 

23 

Feature Integrity VM v6.1 vPars v6.1 

CPU: Granularity Sub-core (as little as 5%) Core 

CPU: Dynamic Enable/Disable, Entitlements Online CPU Add/Delete 

CPU: Scalability 16 Server cores minus VSP resources 

RAM: Scalability 128GB Server RAM minus VSP resources 

RAM: Dynamic Yes (Dynamic & Automatic) No 

STORAGE: AVIO Legacy AVIO Re-architected AVIO 

STORAGE: NPIV Yes Yes 

NETWORK: AVIO Legacy AVIO Re-architected AVIO 

NETWORK: DIRECT Yes Yes 


vPars & Integrity VM v6.1 comparison (part 2) 

24 

Feature Integrity VM v6.1 vPars v6.1 

Migration Support Online & Offline Offline 

Oracle RAC Certified No Yes (ASM & CFS supported) 

Supported VSP Server All Integrity Servers i2 blades, SD2, rx2800 i2 

Supported VSP OS 11i v3 March 2012 11i v3 March 2012 

Supported Guest OS 

* i2 blades and 

pre-Tukwila 

servers only 

* 11i v3 March 2010 

11i v3 September 2010 

11i v3 March 2011 

11i v3 September 2011 

11i v3 March 2012 


11i v3 September 2011* 

11i v3 March 2012 

* i2 blade 

servers only

vPars & Integrity VM Support Going Forward 

Customers using: 

25 

• Legacy DSFs 

• VIO 

• 11i v2 Guests 

• OpenVMS Guests 

Should remain on 

Integrity VM v4.3 


Nov 2011 March 2012 Fusion 

Future 

vPars (Legacy) Continued support on future 11i v3 Fusions 

vPars (SD2) Continued support on future 11i v3 Fusions 

VM v4.3 

vPars v6 

Ships on 1103/1109 Supported on 1103/1109 

Replaced 

on OE 

Web Release vPars & Integrity VM v6


Performance characterization 




Test Ring 

27 

bl890c i2 VSP 

bl860c i2 Native 


EVA4400 w/ SSD Disks 

ProCurve 5412zl

vPars & Integrity VM v6.1 guest configuration 

28 

• Hardware configuration 

– 8 CPU Cores, 100% Entitlement (VM) 

– 64 GB RAM 

– Dual 8GB Fibre Channel NPIV vHBA 

– Dual 10GBE vNICs (AVIO or DIO) 


• Software configuration 

– HP-UX 11i v3 March 2012 Release 

– Default Kernel Tunable Settings 

– PHSS_37042 (Oracle) / PHKL_41967 (DP)

Oracle/Swingbench configuration 

Swingbench v2.3.0.422 / Datagenerator v0.4.0.198 

• v2.4 Workload Profile 

29 

• Greatly reduces latch contention 

• Think Time: 1–2 ms 

• 100 Users 

• Test Run: 30 mins 

• AWR Snapshots: 10/30 mins 


Oracle/Swingbench performance results 

85GB Oracle instance, 40GB memory target 

30 

Oracle Transactions per Second 

95.8% 96.3% 

Native vPar AVIO vPar DIO VM AVIO VM DIO 


80% 80.6%

Data protector benchmarking 

Exercises both networking and storage 

31 

Note 

Be sure PHKL_41967 

is installed on systems 

running Data Protector 


Data Protector Performance Results 

Network backup to NULL device, 10x1GB datasets, 10 backup threads 

32 

Network Backup Performance 

94.6% 94.6% 



73% 

81%

iozone 

Stress AVIO/NPIV storage subsystem 

Different Workloads 

33 

• Read & Write 

• Sequential & Random 

Varying Request Size 

Multiple Instances 


iozone – sequential I/O performance results 

10 simultaneous reader/writer threads, 10GB dataset 

34 

1KB Write 8KB Write 1MB Write 1KB Read 8KB Read 1MB Read 

Native vPar VM 


iozone – random I/O performance results 

10 simultaneous reader/writer threads, 10GB dataset 

35 

Key Point 

AVIO performs 

better in a 

vPar than a VM 

1KB Write 8KB Write 1MB Write 1KB Read 8KB Read 1MB Read 

Native vPar VM 


Key Point 

Larger I/O sizes 

perform better 

inside a VM

netperf 

Stress AVIO and DIO networking subsystems 

Different Workloads 

36 

• Request/Response 

• Outbound Stream 

• Inbound Stream 

Varying Packet Size 

Multiple Instances 


netperf – outbound/inbound stream results 

37 

Out (1 thread) Out (16 threads) In (1 thread) In (16 threads) 



netperf – request/response results 

38 

Key Point 

DIO makes a 

big difference 

in network 

workloads 

Large In 

Large In 

Large Out 

Large Out 

(1 thread) 

(16 threads) 

(1 thread) 

(16 threads) 



Key Point 

AVIO performs 

better in a 

vPar than a VM


Summary and futures 



vPars & Integrity VM v6.1 are ready to handle your 

demanding workloads! 

• v6.1 adds significant customer-requested features 

40 

– Direct I/O for Networking 

– vPar Migration & Transformation 

– i2 Blades, Superdome 2 and rx2800 i2 Server Support 

• vPars/VMs have differentiating strengths and capabilities 

– Need near-native performance? � vPars and Direct I/O Networking 

– Need sub-core CPUs, Dynamic Memory, Online Migration? � Integrity VMs 


Features planned for vPars & Integrity VM v6.1.5 

Shipping in the September 2012 Fusion OE 

41 

� Poulson Processor Pre-enablement 

� HP-UX 11i v2 Virtual Machine Guests 

� APA inside vPar/VM with Direct I/O Adapters 

� Expanded NPIV configurations 

� Relaxed FC Switch requirements during vPar/VM Migrations 

� Increased NPIV limits (32 Virtual HBAs per Physical FC Port) 


Help prioritize future virtualization enhancements 

42 

• vPar / VM Coexistence 

• vPar Dynamic Memory OL* 

• Dynamic I/O Adapter OL* 

• OpenVMS VM Guests 

• Expanded VM Scalability 

– 32 CPU Cores / 256GB RAM 


• Online VM migration changes 

– Direct I/O device support 

– Tukwila �� Poulson 

• Storage enhancements 

– Direct I/O for storage 

– NPIV Storage QoS 

– Emulex NPIV support 

• Matrix OE Integration (gWLM) 

What other vPars & VM features are important to you and why?

43 


Download Now 

Get the Mobile App 

Download content from this session 

with the free Mobile App. 

Text the word “Discover” to 474747 

or: m.hp.com/events

Find out more 

44 

Attend these sessions 

• HOL2202: Hands on with new vPars 

v6.1 

Thursday 1:30 PM 

Visit these demos 

In the Converged Infrastructure 

Pavilion: 

• HP Virtualization Continuum 

for HP-UX Demo 


After the event 

• Contact your sales rep 

• Go to the www.hp.com and 

search for “HP Virtualization 

Continuum for HP-UX” 

Your feedback is important to us. Please take a few minutes to complete the session survey.

Thank you

vPars & Integrity VM v6.1 comparison - HP Discover Online 2012 ...

Create successful ePaper yourself

Delete template?

Save as template?