Doubts in HPUX.

[sudhapage]

Dear All,

I have some doubts in HPUX, kindly send the solution for my doubts.

1. In single user mode, what are all the filesystem are mounted?

2. Kernel update procedure for 11.11

3. While creating volume group, in mknod command after 0x what I have to give, pls explain it.

4. Is there any difference between JFS & VXFS? (or) both are same?

5. Already in one server 10 harddisks are there, if connect 2 new harddisks How I can find it?

6. If I have two ethernet cards, How I can set the ip address for secondary ethernet card using set_parms?

7. How we can find one server in cluster & VPAR/NPAR environment?

Regards,
Sudhakaran.K

[Torsten. · Accepted solution]

So many questions.

1) only / and /stand are mounted; only vg00 is activated;
run "mount -a" to get all vg00 lvols mounted

2) it depends what you want to "update"

3) must be unique; best practice is to use the same number as the VG (vg01 => 0x010000)

5) "in" one server or connected to the server?
run "ioscan -fnCdisk" before and after and compare; if added online, there are no device files for the new disks

6) this works only with 11.31; but you can use SAM

7) Did you lost it?
Don't understand the question, sorry.

[sudhapage]

Hi Torsten,

My seventh question is:

7) I am logging to one server, In that server how we can find whether that server configured in cluster environment (or) VPAR/NPAR environment?

Regards,
Sudhakaran.K

[Torsten.]

forgot 4)

JFS=VxFS,
"Beginning with HP-UX 10.0, Hewlett-Packard began providing a Journaled File System (JFS)
from VERITAS Software Corporation known as the VERITAS® File System⠢ (VxFS®)"

7)
may be some complex, but
if "cmviewcl" gives results, you are in a cluster;

if "vparstatus" gives results, you are in a vPar config

if both commands return results, you are in a clustered vPar.

[Geoff Wild]

3. While creating volume group, in mknod command after 0x what I have to give, pls explain it.

Remember - that is a HEX number - so - convert your VG to hex.

IE:

for vg05 it would be 0x050000
for vg10 it would be 0x0a0000

Why?

Look at your kernel parameter maxvgs.

Say it is 80.

You have been all along creating the minor number with the first digits being the same a s the vg number...

So, you try to make say vg51

Guess what - it will fail - as 0x51000 equates to 81 in decimal - and your maxvgs is 80!

Rgds...Geoff