would vparefiutil -d cause any problems on nPar?

[Hanry Zhou]

I did "vparefiutil -d" on a nPar system, and then when I found out the mistake, I did "vparefiutil -u". The system could reboot without a problem, as far as I can see.

Would this incident cause any problmes?

Thanks,

[Matti_Kurkela]

As far as I understand, the "vparefiutil" command affects the vPar database only. As a nPar system normally does not even have a vPar database and won't use it for anything, there should be no problems.

MK

[Torsten.]

You wrote "nPar" system, but I think there is vPar running (you won't have the command otherwise).

From the manual:
vparefiutil Unix shell command to display or manage the HP-UX hardware path to EFI path
mappings of bootable disks within the vPars database.

and later

â To delete the old entries and update with the new entries:
# vparefiutil -d
# vparefiutil -u

Exactly what you did. So everything looks good now.

[Hanry Zhou]

It is on nPar where I ran "vparefiutil -d" and then "-u". It seems like it doesn't effect nPar.

but, I do have /stand/vpdb, this file may come from somewhere else, because this nPar ed from another sever.

Could I or should I remove /stand/vpdb in this case? what is an appropriate way to remove it?

[Torsten.]

If you have this file /stand/vpdb - you probably need it.
What gives "vparstatus"?

[Hanry Zhou]

#vparstatus
vparstatus: Warning: Not accessing live monitor database, Requested resources shown.

Again, this is a Npar system, so, do I really need /stand/vpdb, if not, could I remove it?

[Hanry Zhou]

this npar server was initially ignited from the ther image, so it is very likely /stand/vpdb was copied from that image.

[Hanry Zhou]

Can somoebody please take a look at this question?

Thanks!

[Reshma Malusare]

Hi Hanry,

1] vparefiutil -->manage the HP-UX hardware path to EFI path of bootable disks within the vPars database.

So you delete & then update datbase.. so it will not affect npar. As you are handling vpar dtabase.

2] From your vparstatus output, it is clear that local copy of /stand/vpdb is not able to synchrinize with master copy of vpar monitor.
As, there continous synchronization in these two files to keep update on file.

3] So you know /stand/vpmon refers /stand/vpdb while booting as this databse contains configuration information of vpar.so it always recommended to keep several copies of it.

4] Now, read this document which will answer your question to keep copy or not?
http://docs.hp.com/en/T1335-90018/ch05s03.html

Thanks & Regards
Reshma