topic Re: Error with parstatus in Operating System - HP-UX

Error with parstatus

Jose_129 — Mon, 16 Jan 2006 15:28:33 GMT

I have server rp7410 with HPUX 11.11, when executed the command vparstatus, display the message:

BKUXCONT >parstatus
Error: Unsupported platform. Command aborted. (-12)

Which is the problem?

Regards,

Jose

Re: Error with parstatus

Olivier Masse — Mon, 16 Jan 2006 15:32:48 GMT

Are you talking about parstatus or vparstatus?

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 15:43:19 GMT

Command parstatus.

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 16:04:00 GMT

Any News

Re: Error with parstatus

Geoff Wild — Mon, 16 Jan 2006 16:05:55 GMT

which parstatus

Should be
/usr/sbin/parstatus

file /usr/sbin/parstatus
/usr/sbin/parstatus: PA-RISC1.1 shared executable dynamically linked

Unsupported platform? sounds like maybe you have the IA64 version on a parisc box?

Rgds...Geoff

Re: Error with parstatus

Geoff Wild — Mon, 16 Jan 2006 16:08:56 GMT

Also see this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=716083

Rgds...Geoff

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 16:13:15 GMT

BKUXCONT >model
9000/800/rp7410

The command parstatus is executed of:
BKUXCONT >/usr/sbin/parstatus
Error: Unsupported platform. Command aborted. (-12)

Any news.

Regards,

Jose

Re: Error with parstatus

Geoff Wild — Mon, 16 Jan 2006 16:13:44 GMT

My last post look more like it - see page 37 of this:

http://docs.hp.com/en/5185-4304/5185-4304.pdf

It talks about the hd_fabric Driver as well...

Rgds...Geoff

Re: Error with parstatus

Sameer_Nirmal — Mon, 16 Jan 2006 16:18:35 GMT

Hi,

This error could occur if you have ignited the rp7410 server which is multi-platform server using the ignite image of a single platform server line N4000 causing incompatibility problem.

If you are using N4000 ignite-image you need to ensure "hd_fabric" driver added in the kernel. Rebuild the kernel and reboot.

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 16:20:00 GMT

The hd_fabric is configured in /stand/system, reboot the server but the same error.

BKUXCONT >strings system | grep -i hd_fabric
hd_fabric

Any News.

Jose

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 16:22:01 GMT

My server is rp7410 and i don't have N4000.

Regards,

Jose

Re: Error with parstatus

Geoff Wild — Mon, 16 Jan 2006 16:39:39 GMT

Again do the which parstatus command...

then do a what on it - should look like:

# what /usr/sbin/parstatus
/usr/sbin/parstatus:
main.c $Date: 2004/09/19 23:43:29 $Revision: r11.11/1 PATCH_11.11 (PHCO_31878)
display_complex.c $Date: 2003/03/11 17:37:07 $Revision: r11.11/3 PATCH_11.11 (PHCO_28769)
display_cabinet_status.c $Date: 2003/12/19 01:44:35 $Revision: r11.11/4 PATCH_11.11 (PHCO_30076)
display_cell_status.c $Date: 2004/03/17 21:38:48 $Revision: r11.11/4 PATCH_11.11 (PHCO_30585)
display_chassis_status.c $Date: 2003/03/11 17:37:07 $Revision: r11.11/1 PATCH_11.11 (PHCO_28769)
display_pd_status.c $Date: 2003/03/11 17:37:07 $Revision: r11.11/2 PATCH_11.11 (PHCO_28769)
fill_all_details.c $Date: 2003/03/11 17:37:07 $Revision: r11.11/1 PATCH_11.11 (PHCO_28769)
fill_components_info.c $Date: 2003/03/11 17:37:07 $Revision: r11.11/1 PATCH_11.11 (PHCO_28769)
core_common.c $Date: 2003/03/11 17:37:07 $Revision: r11.11/3 PATCH_11.11 (PHCO_28769)
profile_ctl.c $Date: 2003/03/11 17:37:07 $Revision: r11.11/1 PATCH_11.11 (PHCO_28769)
$Revision: @(#) parmgmt R11.11_BL2004_1003_3 PATCH_11.11 PHCO_31878

See if you have those patches...

Rgds...Geoff

Re: Error with parstatus

Sameer_Nirmal — Mon, 16 Jan 2006 16:52:44 GMT

Jose,

You seems to be very fast putting your feedback against the replies which is good.

In my previous post I referred using "N4000 ignite image" and NOT saying server as N4000.
Have you ignited this server with single platform server ignite image??

Even you see the "hd_fabric" driver in the /stand/system, it doesn't mean it is installed in the current running kernel. You can check if a driver is configured in running kernel using "lsdev" command.

If it is not already in the kernel and it is in /stand/system, you just need to rebuild the kernel using "/usr/sbin/mk_kernel" command and reboot.

I see in your profile at
http://forums1.itrc.hp.com/service/forums/publicProfile.do?userId=CA1216064&forumId=1
"I have assigned points to 2 of 63 responses to my questions"

which is not good. Be fast to to make it 63-63 as well.

Re: Error with parstatus

Geoff Wild — Mon, 16 Jan 2006 17:01:34 GMT

Sameer,

I'm not too sure about that - I don't have hd_fabric when I do a lsdev...and parstatus works on my 7410's.

# lsdev
Character Block Driver Class
0 -1 cn pseudo
1 -1 asio0 tty
2 -1 SCentIf unknown
3 -1 mm pseudo
4 -1 olar_psm_if olar
5 -1 dev_olar olar
6 -1 devkrs pseudo
7 -1 lpr0 unknown
8 0 sioflop unknown
8 0 sioflop unknown
10 -1 hcd unknown
11 -1 usbd unknown
12 -1 hub unknown
13 -1 hid unknown
14 -1 btlan lan
15 -1 maclan lan
16 -1 ptym ptym
17 -1 ptys ptys
18 -1 ip pseudo
19 -1 arp pseudo
20 -1 rawip pseudo
21 -1 tcp pseudo
22 -1 udp pseudo
23 -1 stcpmap pseudo
25 -1 nuls pseudo
26 -1 netqa pseudo
27 -1 dmem pseudo
28 -1 diag0 diag
31 -1 tun pseudo
32 -1 telm strtelm
33 -1 tels strtels
36 -1 tlclts pseudo
37 -1 tlcots pseudo
38 -1 iomem pseudo
44 -1 tlcotsod pseudo
45 -1 fcT1_cntl lan
46 -1 netdiag1 unknown
48 -1 fcp fcp
49 -1 td fc
50 -1 fddi4 lan
51 -1 iop_drv i2o
54 -1 gvid unknown
57 1 dmp vxvm
58 2 vol vxvm
61 -1 vols vxvm
62 -1 fddi3 unknown
63 -1 pcitr unknown
64 64 lv lvm
67 -1 cxperf pseudo
68 -1 cifs pseudo
69 -1 dev_config pseudo
72 -1 clone pseudo
73 -1 strlog pseudo
74 -1 sad pseudo
75 -1 func0 tty
76 -1 ipmi ipmi
77 3 emcp pseudo
78 -1 krm pseudo
79 -1 evp pseudo
97 97 vxportal unknown
116 -1 echo pseudo
119 -1 dlpi pseudo
156 -1 ptm strptym
157 -1 pts strptys
164 -1 pipedev unknown
183 -1 diag1 diag
188 31 sdisk disk
189 -1 klog pseudo
203 -1 sctl ctl
205 -1 stape tape
207 -1 sy pseudo
212 -1 tape0 tape
227 -1 kepd pseudo
232 -1 diag2 diag

Rgds...Geoff

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 17:41:36 GMT

BKUXCONT >mk_kernel
Generating module: krm...
Compiling /stand/build/conf.c...
Loading the kernel...
Generating kernel symbol table...
BKUXCONT >more /stand/system | grep -i hd_fabric
hd_fabric

Now shutdown the server.

Regards,

Jose

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 17:49:57 GMT

Then the shutdown -ry 0, show the message:

BKUXCONT >lsdev | grep -i hd_fabric
BKUXCONT >

The Software installed:

BKUXCONT >swlist -l fileset | grep -i parmgr
PartitionManager.PARMGR B.11.11.01.06 Partition Management
PartitionManager.PARMGR-HELP B.11.11.01.06 Partition Manager On-line Help
PartitionManager.PARMGR-MAN B.11.11.01.06 Partition Manager Manual Pages

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 18:48:37 GMT

The driver hd_fabric is installed:

BKUXCONT >kmsystem | grep -i hd_fabric
hd_fabric Y -

Re: Error with parstatus

Jose_129 — Mon, 16 Jan 2006 19:09:23 GMT

Any News,

Regards,

Jose

Re: Error with parstatus

Patrick Wallek — Mon, 16 Jan 2006 19:31:37 GMT

Do you still get an error when you run the command?

Can you please post the information Geoff has asked for:

# which parstatus

# what $(which parstatus)

Re: Error with parstatus

Sameer_Nirmal — Mon, 16 Jan 2006 23:06:07 GMT

Geoff,

I recalled that "hd_fabric" is "kernel module" which acts as interface/driver for npar commands like "parstatus" "parmgr" etc.
Once included, it gets statistically linked to the kernel. The "lsdev" command can only list device drivers configured into the system ( fetched from running kernel) which are installed using a separate kernel routine having charactristics as "class" "major no" "minor no" etc.

For kernel module, these commands could be used to know the module status.
# kmsystem -q hd_fabric
# kmadmin -Q hd_fabric

Jose,
Does the "parstatus" works now?
Run the above commands to ensure the module installed successfully. Now assuming the module is loaded correctly, then check for command level patches for "parstatus" as mentioned by Geoff.