topic Re: Identifying server type in Operating System - HP-UX

Identifying server type

Stephen Keane — Wed, 26 Jan 2005 11:26:29 GMT

What's a quick way of determinging if a server is a V class.

I don't have a V class server, but I'm guessing the answer would be along the lines of either uname or model.

Can anyone with a V class server post the results of 'uname -a' and/or 'model'?

What's so different about V class servers, even Ignite treats them differently?

Re: Identifying server type

Tom Danzig — Wed, 26 Jan 2005 11:32:40 GMT

Use the model command

Re: Identifying server type

Stephen Keane — Wed, 26 Jan 2005 11:35:17 GMT

If I do model on a J series I get

9000/785/J5000

On a B1000, I get

9000/785/B1000

I can't just reply on the first character after the second '/' being V presumably?

Re: Identifying server type

A. Clay Stephenson — Wed, 26 Jan 2005 11:38:44 GMT

The V-boxes are very different because they were actually manufactured by Convex Computer Corp which was later acquired by HP.

Re: Identifying server type

Tom Danzig — Wed, 26 Jan 2005 11:38:48 GMT

I'm almost certain it will be a V. I used to work with a V class, however, I no longer do and cannot confirm.

Re: Identifying server type

Patrick Wallek — Wed, 26 Jan 2005 11:40:38 GMT

It should be something like the following:

9000/800/V2200
9000/800/V2000
9000/800/V2250
9000/800/V2500
9000/800/V2600
9000/800/V2650
9000/800/V2700

Note: I got these value from the /etc/.supported_bits file on one of my 11.0 systems. This should match the output of the model command.

Re: Identifying server type

Steven E. Protter — Wed, 26 Jan 2005 11:41:14 GMT

model command should be do it.

Every line has its unique design issues. What about Ignite is different?

SEP

Re: Identifying server type

Sundar_7 — Wed, 26 Jan 2005 11:44:03 GMT

This is what I get for my V2250

9000/800/V2250

V class is an "odd ball" HP server, I would say :-). It has something called Open Boot Prompt (similar to the Sun SPARC architecture).

Even though V class is a 64 bit architecture, an ignite tape created on a V class cannot be restored to an another 64 bit system, since the boot kernel is different.VINSTALL is the kernel name used for booting V-class server by the ignite.

You will have a A-Class server used for administration purpose(similar to SMS used for superdome).

It has some similarites to superdome. I believe it uses the same chipset as some of the old superdome servers (PA8700).

Re: Identifying server type

Stephen Keane — Wed, 26 Jan 2005 11:49:59 GMT

So something along the lines of

model | awk 'FS="/" { print $3 }' | cut -c1

Would indicate whether it was a V class or not?

Ignite uses a different install kernel (VINSTALL) for V class servers, determining the bit-size of the kernel lets you know whether to use INSTALL or WINSTALL, but I needed to exclude V classes from the mix.

Re: Identifying server type

Sundar_7 — Wed, 26 Jan 2005 12:00:04 GMT

Yes your awk will tell you if it is a V-class server.

Ignite uses VINSTALL for v-class servers.
I believe INSTALL is for 64-bit servers and WINSTALL is for systems that support both 32 and 64 bit HP-UX.

# getconf HW_CPU_SUPP_BITS

Will tell you the OS word widths your CPU is capable of supporting.

Re: Identifying server type

Gordon Morrison_1 — Wed, 26 Jan 2005 12:03:28 GMT

machinetype=`model`;echo ${machinetype##*/}
will filter out everything up to and including the last '/' character

Re: Identifying server type

Stephen Keane — Wed, 26 Jan 2005 12:20:24 GMT

getconf HW_CPU_SUPP_BITS

on my J class and B class servers returns 64
(with hpux 11.11 installed) and Ignite uses WINSTALL. Does this mean that if getconf HW_CPU_SUPP_BITS returns 32, then Ignite will use INSTALL?

Re: Identifying server type

Patrick Wallek — Wed, 26 Jan 2005 12:26:36 GMT

Stephen,

Yes, that's correct.

With Ignite, IIRC, INSTALL is for 32-bit kernels, WINSTALL is for 64-bit and VINSTALL is for V-series machine ONLY.

Re: Identifying server type

Stephen Keane — Wed, 26 Jan 2005 12:29:16 GMT

I think I've got all the information I needed, thanks.