topic Re: vparstatus: Error: -d US: Illegal hardware path specification in Operating System - HP-UX

vparstatus: Error: -d US: Illegal hardware path specification

Shibin_2 — Mon, 10 Mar 2008 01:14:46 GMT

Hi,

I am a kid on vPar. One of my box is keep on alerting the titled error. How do I rectify it? Is it related to efi hardware path ?

Appreciate your valuable helps.

Thanks

Re: vparstatus: Error: -d US: Illegal hardware path specification

Shibin_2 — Mon, 10 Mar 2008 02:05:33 GMT

## Addition

Can I do vparefiutil -u ??
Is there any issue to apply this cammand ?

Re: vparstatus: Error: -d US: Illegal hardware path specification

Mridul Shrivastava — Mon, 10 Mar 2008 03:14:40 GMT

Where do you receive this error ? or do you get this error whenever vpastatus is executed ??

As far as vparefiutil is concerned, I don't think it is related to the error message.

I think that incorrect (Illegal) HW path has been assigned to the vpar, which actually doesn't exist. Could you please collect the list of the LBAs assigned to all the Vpars and check if they really exist?

Whats the server model so you can get the list of hw paths/ LBA for that server, serach for the block diagram and I m sure u will get one.

Re: vparstatus: Error: -d US: Illegal hardware path specification

Shibin_2 — Mon, 10 Mar 2008 03:24:41 GMT

It's a superdom box. It had a reboot on the last weekend. After rebooting, OVO is sending alert as on the title. But I couldn't find any errors on syslog or anywhere.

(root)> model
ia64 hp superdome server SD16B

Re: vparstatus: Error: -d US: Illegal hardware path specification

Mridul Shrivastava — Mon, 10 Mar 2008 03:37:38 GMT

Was it a normal reboot??

If it was not a normal one there could be some hardware issue.

Re: vparstatus: Error: -d US: Illegal hardware path specification

Shibin_2 — Mon, 10 Mar 2008 03:49:10 GMT

Yeah. It was a scheduled reboot. But parstatus and vparstatus commad doesn't return any errors.

Re: vparstatus: Error: -d US: Illegal hardware path specification

Shibin_2 — Tue, 01 Apr 2008 02:18:29 GMT

Thanks guys.

It was actually the script error.