topic GSP Commands not permitted in Operating System - HP-UX

GSP Commands not permitted

Konrad Hegner — Thu, 21 Jul 2005 01:20:14 GMT

Hello all

I can find here some post about the GSP resetting.
Now I had also a problem with GSP and would reset it with following command:
# stty +resetGSP < /dev/GSPdiag2
And it gave me no permission:
'This operation is not permitted'

The same output with following command:
# stty +queryGSP < /dev/GSPdiag2.

I am root. I tried it with a telnet and rlogin session. Because it wasn't possible to connect from local

What is wrong, why have I only GSPdiag2 and not GSPdiag1 (too), who know a good manual?
Thanks Konrad

Re: GSP Commands not permitted

Warren_9 — Thu, 21 Jul 2005 01:29:03 GMT

hi,

what is the output of "lssf /dev/GSP*"?

Re: GSP Commands not permitted

Konrad Hegner — Thu, 21 Jul 2005 01:33:29 GMT

This is the output:

host,sys,root # lssf /dev/GSP*
asio0 card instance 0 port 0 transparent at address 0/0/4/1 /dev/GSPdiag2

Re: GSP Commands not permitted

Warren_9 — Thu, 21 Jul 2005 01:38:47 GMT

if your GSPdiag1 is missing, try to re-install the device.
# insf -e -d asio0
# ioscan -fnC tty <-- to verify

Re: GSP Commands not permitted

Konrad Hegner — Thu, 21 Jul 2005 01:49:40 GMT

Warren
I do not really miss GSPdiag1, but I'm not shure is this a 'killer'-factor for my command.

When I work with insf, there would use the same file:
host,sys,root # insf -e -d asio0
insf: Installing special files for asio0 instance 0 address 0/0/4/1
host,sys,root # ioscan -fnC tty
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
tty 0 0/0/4/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag2 /dev/diag/mux0 /dev/mux0 /dev/tty0p0 /dev/tty0p1

Of corse, because the old one is still present. It is posible to remove first the /dev/GSPdiag2?
If yes, how, and what's happen with the other files (mux0, tty0p0)?

Re: GSP Commands not permitted

Devender Khatana — Thu, 21 Jul 2005 23:06:21 GMT

Hi,

Yes you can remove the device file for /dev/GSPdiag2 & recreate it. /dev/mux0 & /dev/tty0p0 etc. are the file associated with this instance & will be created while doing a insf.

Do it from a telnet session.

#rmsf -H 0/0/4/1
#insf -e

The new device file should not be /dev/GSPdiag1 only.

HTH,
Devender

Re: GSP Commands not permitted

Ermin Borovac — Fri, 22 Jul 2005 00:08:38 GMT

Please check that major and minor number of GSPdiag2 device file match the listing below.

crw------- 1 root sys 1 0x000080 May 28 2003 /dev/GSPdiag2

Also, what is the hardware model of your server?

Re: GSP Commands not permitted

Konrad Hegner — Fri, 22 Jul 2005 02:26:07 GMT

Ermin

This is the file:
crw------- 1 root sys 1 0x000080 Jan 9 2003 GSPdiag2

And it is a rp5430

I didn't remove yet the file like described from Devender (no time - busy in office).
Do you think, it is a 'bad' idea to remove and recreate the file?

Re: GSP Commands not permitted

Ermin Borovac — Mon, 25 Jul 2005 00:55:28 GMT

You can safely remove the file and rerun insf to recreate it.

# insf -d asio0 -ev
insf: Installing special files for asio0 instance 1 address 0/0/4/1
making GSPdiag1 c 1 0x010080

If insf doesn't create the special file as shown above then you need to install the following patches.

If your O/S is 11.00

Patch Name: PHNE_29519
Patch Description: s700_800 11.00 Cumulative Mux and Pty Patch

Patch Name: PHCO_27370
Patch Description: s700_800 11.00 mksf(1M) cumulative patch

If your O/S is 11.11

Patch Name: PHNE_30463
Patch Description: s700_800 11.11 Cumulative Mux and Pty Patch

Patch Name: PHCO_32202
Patch Description: s700_800 11.11 mksf(1M) cumulative patch

Please note that mux/pty patch requires server reboot.