Enabling/Disabling standby processors and memory on a GS1280

[Jim Geier_1]

A site I am working with part-time is about to complete installation a GS1280 with 32 processors, 16 of which will be on standby, and 32 GB of memory with 16 GB on standby. The system will be configured with two hard partitions and added to an existing OpenVMS V7.3-2 cluster. I have looked for but not found documentation on the process or the actual steps to enable or disable processors or memory when needed. Can someone point me to the documentation or outline the steps involved?

(I apologize if this should be in the hardware forum, but while it is hardware-specific, it seems to be a system management function.)

Thanks!

[Ken Robinson]

If VMS is already booted, you can do a

$ stop/cpu

But you have to be carefull when doing this to make sure the CPUs you're stopping aren't handling IO.

If VMS is not booted, I believe (someone will probably correct me if I'm wrong) you need to stop the CPUs in MBM. To get into MBM, type MBM at the >>> prompt. (MBM must be in capital letters).

I'm not sure about the memory.

Ken

[Robert_Boyd]

You'll probably want to look at the GS1280 User Guide and the HP OpenVMS Alpha Partitioning and Galaxy Guide(formerly titled: OpenVMS Alpha Galaxy Guide)

For V7.3-2 version http://h71000.www7.hp.com/DOC/732FINAL/aa-rezqe-te/aa-rezqe-te.HTMl

At the DCL prompt you can check the HELP SET CPU and HELP STOP /CPU and HELP START/CPU

Robert

[Fodil ATTAR]

Hi Jim,

I hope the attached file will be helpfull.
For action on console state for migrate cpu.

If VMS is booted, From what I remember there is a trick.

Each QBB get 4 CPU (0 AND 1,2,3)
(4 AND 5,6,7) CPU 0 and 4 are Primary CPU AND MUST NOT BE MOVED.

Imagine you got 2 partitions one called PART1 & PART2

to see the cpu do

PART1_node> $show cpu/briefs

for example PART1 get 5 CPU (0,1,2,3,5) & PART2 get 3 CPU (4,6,7).

We want to migrate one cpu from PART1 to PART2. The cpu 1 will be migrated.

We go on node PART1 and we push the cpu to PART2. (BUT WE DON't touch CPU 0 and 4)

PART1_node>$ stop/cpu/migrate=PART2 1

Regards,

Fodil.

[Ian Miller.]

Is this system using the iCAP hp offering?

[Jim Geier_1]

Yes, This system is using the HP iCAP (instant capacity) program. I have learned that the memory will always be on -- iCAP apparently does not provide for turning on and off memory. So do the normal START/CPU and STOP/CPU commands apply to the iCAP program?

[Ian Miller.]

I did not think that iCAP was supported by VMS until V8.3 (on HPUX you pay hp some money, get a activation keyword which when entered in some software switches on the CPU).
I guess you need to talk to the people that sold you iCAP to see how its supposed to work.

[Jim Geier_1]

No further information in this thread...closing.