Planning
cancel
Showing results for 
Search instead for 
Did you mean: 

rp8400/vpar hardware requirements

SOLVED
Go to solution
Peter Heinemann
Frequent Advisor

rp8400/vpar hardware requirements

We have a number of rp8400s that are due to be vpar'd next year. These are san-connected for data, local mirrored disk for the o/s. I wanted to confirm some impressions gained from a few articles.
The current slot layout is:

1 - HP Tachyon TL/TS Fibre Channel Mass Storage Adapte
2 - HP Tachyon TL/TS Fibre Channel Mass Storage Adapte
3 - HP A4929A PCI 1000Base-T Adapter
4 - HP A5506B PCI 10/100Base-TX 4 Port
5 - HP A5506B PCI 10/100Base-TX 4 Port
6 - empty
7 - empty
8 - empty

1) true that for connection to the san, EACH vpar will need one (or two for redundancy) FC card(s)?

2) what about network connections? same requirement?
each server has two HP A5506B PCI 10/100Base-TX 4 Port cards. Would these cards be shareable across the vpars?

the lan shows as:
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
lan 0 0/0/0/1/0 gelan CLAIMED INTERFACE HP A3639-60019 1000Base-T Built-in I/O
lan 1 0/0/6/0/0 gelan CLAIMED INTERFACE HP A4929A PCI 1000Base-T Adapter
lan 2 0/0/12/0/0/4/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan2 /dev/ether2 /dev/lan2
lan 3 0/0/12/0/0/5/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan3 /dev/ether3 /dev/lan3
lan 4 0/0/12/0/0/6/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan4 /dev/ether4 /dev/lan4
lan 5 0/0/12/0/0/7/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan5 /dev/ether5 /dev/lan5
lan 6 0/0/14/0/0/4/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan6 /dev/ether6 /dev/lan6
lan 7 0/0/14/0/0/5/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan7 /dev/ether7 /dev/lan7
lan 8 0/0/14/0/0/6/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan8 /dev/ether8 /dev/lan8
lan 9 0/0/14/0/0/7/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100Base-TX 4 Port
/dev/diag/lan9 /dev/ether9 /dev/lan9

Thanks in advance...
..Peter
4 REPLIES
harry d brown jr
Honored Contributor
Solution

Re: rp8400/vpar hardware requirements

peter,

1) true that for connection to the san, EACH vpar will need one (or two for redundancy) FC card(s)?

** It depends upon your redundancy requirements - I personally require at LEAST Two!!


2) what about network connections? same requirement?
each server has two HP A5506B PCI 10/100Base-TX 4 Port cards. Would these cards be shareable across the vpars?


NO!!!! an IO card CAN NOT BE SHARED between vPars!!

Each vPar will require it's OWN :

CPU
LAN IO CARD
DISK IO CARD


They only share MEMORY - well not really - memory is divided up between the partitions, but NEVER is the same memory address shared amongst the other partitions!!!


The same is true with HARD Partitions, especially since you can HARD partition the RP8400!

Of course EACH HARD Partition can have vPar partitions within it!

Here are your four cards:

(1) lan 0 0/0/0

(2) lan 1 0/0/6

(3) lan 2 0/0/12
(3) lan 3 0/0/12
(3) lan 4 0/0/12
(3) lan 5 0/0/12

(4) lan 6 0/0/14
(4) lan 7 0/0/14
(4) lan 8 0/0/14
(4) lan 9 0/0/14

One CARD -> One partition!! Well at least for today. I've expressed my desire to be able to share cards, especially those like the four port lan cards!! maybe some day!!


Peter, I've been running vPars for TWO years now, almost since day one of the beta program for vPars.



live free or die
harry
Live Free or Die
Peter Heinemann
Frequent Advisor

Re: rp8400/vpar hardware requirements

Thanks, Harry. That's what I suspected. Time for management to digest the news...

...Peter
Peter Heinemann
Frequent Advisor

Re: rp8400/vpar hardware requirements

Couple more questions:

1) Can vpars span cells within a hard partition?

i.e., if there are two cells each with 4 cpus, can you configure a vpar of 6cpus and a second of 2?

2) re: Harry Brown -- you listed the following config. in your beta:
"6 partitions (6 cpu's, 10gb of memory, 6 lan cards, 5 FC cards, and 1 scsi card)"

Given the requirement for unique boot path, you're then booting off a SAN via the FCs? Or does the scsi card give you multiple unique boot paths? How many peripheral disks can be loaded in the superdome? (there are only 4 in the rp8400...)

Thanks!
Tom Maloy
Respected Contributor

Re: rp8400/vpar hardware requirements

Couple more questions:

1) Can vpars span cells within a hard partition?
Yes. In fact, they should span a cell if possible.

i.e., if there are two cells each with 4 cpus, can you configure a vpar of 6cpus and a second of 2?
Yes.

2) re: Harry Brown -- you listed the following config. in your beta:
"6 partitions (6 cpu's, 10gb of memory, 6 lan cards, 5 FC cards, and 1 scsi card)"

Given the requirement for unique boot path, you're then booting off a SAN via the FCs? Or does the scsi card give you multiple unique boot paths? How many peripheral disks can be loaded in the superdome? (there are only 4 in the rp8400...)
You don't have to boot off of the SAN, although that will work. Since a card can't be shared, it will only give you one boot path. On the SuperDome, you will wind up with extra I/O bays holding D2100 disk arrays.

Tom

Carpe diem!