HPE Community
Operating System - HP-UX
1836770 Members
2274 Online
110109 Solutions
New Discussion

Re: Secure Path doesn't work after reboot

 
SOLVED
Go to solution
yyghp
Super Advisor

‎03-17-2005 03:23 AM

‎03-17-2005 03:23 AM

Secure Path doesn't work after reboot

Before I installed Secure Path 3.0D on HP-UX 11iv1, I can see:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 3 0/2/1/0.10.1.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 4 0/2/1/0.10.1.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 5 0/2/1/0.10.1.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 6 0/2/1/0.10.1.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 7 0/2/1/0.10.1.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 9 0/2/1/0.10.1.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 11 0/2/1/0.10.1.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 17 0/2/1/0.10.2.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 18 0/2/1/0.10.2.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 19 0/2/1/0.10.2.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 20 0/2/1/0.10.2.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 21 0/2/1/0.10.2.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 22 0/2/1/0.10.2.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 24 0/2/1/0.10.2.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 8 0/5/2/0.11.1.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 10 0/5/2/0.11.1.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 12 0/5/2/0.11.1.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 13 0/5/2/0.11.1.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 14 0/5/2/0.11.1.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 15 0/5/2/0.11.1.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 16 0/5/2/0.11.1.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 23 0/5/2/0.11.2.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 25 0/5/2/0.11.2.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 26 0/5/2/0.11.2.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 27 0/5/2/0.11.2.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 28 0/5/2/0.11.2.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 29 0/5/2/0.11.2.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 30 0/5/2/0.11.2.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ

After I install Secure Path:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 3 255/255/0/0.0 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d0 /dev/rdsk/c20t0d0
disk 4 255/255/0/0.1 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d1 /dev/rdsk/c20t0d1
disk 5 255/255/0/0.2 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d2 /dev/rdsk/c20t0d2
disk 6 255/255/0/0.3 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d3 /dev/rdsk/c20t0d3
disk 7 255/255/0/0.4 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d4 /dev/rdsk/c20t0d4
disk 8 255/255/0/0.5 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d5 /dev/rdsk/c20t0d5
disk 9 255/255/0/0.6 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d6 /dev/rdsk/c20t0d6

But after I reboot the server, it changed back:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 3 0/2/1/0.10.1.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 4 0/2/1/0.10.1.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 5 0/2/1/0.10.1.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 6 0/2/1/0.10.1.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 7 0/2/1/0.10.1.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 9 0/2/1/0.10.1.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 11 0/2/1/0.10.1.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 17 0/2/1/0.10.2.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 18 0/2/1/0.10.2.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 19 0/2/1/0.10.2.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 20 0/2/1/0.10.2.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 21 0/2/1/0.10.2.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 22 0/2/1/0.10.2.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 24 0/2/1/0.10.2.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 8 0/5/2/0.11.1.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 10 0/5/2/0.11.1.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 12 0/5/2/0.11.1.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 13 0/5/2/0.11.1.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 14 0/5/2/0.11.1.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 15 0/5/2/0.11.1.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 16 0/5/2/0.11.1.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 23 0/5/2/0.11.2.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 25 0/5/2/0.11.2.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 26 0/5/2/0.11.2.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 27 0/5/2/0.11.2.0.0.0.4 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 28 0/5/2/0.11.2.0.0.0.5 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 29 0/5/2/0.11.2.0.0.0.6 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
disk 30 0/5/2/0.11.2.0.0.0.7 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ

Why? Any good idea for me?
Thank you very much !
0 Kudos
23 REPLIES 23
Patrick Wallek
Honored Contributor

‎03-17-2005 04:36 AM

‎03-17-2005 04:36 AM

Re: Secure Path doesn't work after reboot

Did SecurePath rstart when the system came back up? It sounds like it just isn't running.

0 Kudos
John Payne_2
Honored Contributor

‎03-17-2005 05:08 AM

‎03-17-2005 05:08 AM

Solution

Re: Secure Path doesn't work after reboot

One of the versions of SecurePath (I forget if it was 3.0C or 3.0D) failed to be shipped with the startup script. I have attached it here for you if you do not have it. (place it in /sbin/init.d, make the start link in /sbin/rc1.d)

If SecurePath is running, you will see a 'spagent' process running.

Hope it helps

John
Spoon!!!!
0 Kudos
yyghp
Super Advisor

‎03-17-2005 05:49 AM

‎03-17-2005 05:49 AM

Re: Secure Path doesn't work after reboot


I installed same Secure Path ( 3.0D ) on other two boxes, it works fine there.

I check the init file on this box:
# pwd
/sbin/rc1.d

lrwxr-xr-x 1 root sys 19 Mar 17 08:53 K800spinit -> /sbin/init.d/spinit

And the file /sbin/init.d/spinit is the right one.

However, I will check "spagent" when next time I reboot the server.
Thanks !
0 Kudos
yyghp
Super Advisor

‎03-17-2005 06:41 AM

‎03-17-2005 06:41 AM

Re: Secure Path doesn't work after reboot

the server has been rebooted, and spagent is now running:

# ps -ef | grep sp
root 6564 6213 1 14:21:49 pts/td 0:00 grep sp
root 1378 1 0 10:26:20 ? 0:00 spagent

but when I used "ioscan", still have tons of LUNs, it means that the Seure Path is not working:

# spmgr display
Server: srs137.homehardware.ca Report Created: Thu, Mar 17 14:41:01 2005
Command: spmgr display
No LUNs have been presented to Secure Path.

I think if I reinstall Secure Path, it will recover, but it will change back after reboot, why?

Thanks!
0 Kudos
Dave Hutton
Honored Contributor

‎03-17-2005 06:42 AM

‎03-17-2005 06:42 AM

Re: Secure Path doesn't work after reboot

What does spmgr display show?

I know with Securepath it seems like I have to reboot the server a few times before I see things like I like it.
patch the required patches - reboot
install securepath - reboot
present a disk - reboot.

Anyway, what does spmgr display show?
0 Kudos
yyghp
Super Advisor

‎03-17-2005 06:49 AM

‎03-17-2005 06:49 AM

Re: Secure Path doesn't work after reboot

# spmgr display
Server: srs137.homehardware.ca Report Created: Thu, Mar 17 14:45:39 2005
Command: spmgr display
IOCTL PathCtl Config(1585) failed(12): No such device or address
No LUNs have been presented to Secure Path.

strange, I can see the right output of "spmgr display" right after I installed Secure Path:

# spmgr display
Server: srs137.homehardware.ca Report Created: Wed, Mar 16 21:01:03 2005
Command: spmgr display
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Storage: 5000-1FE1-5004-5690
Load Balance: Off Auto-restore: Off
Path Verify: On Verify Interval: 30
HBAs: td0 td1
Controller: P5849E1AAQE04J, Operational
P5849E1AAQF00E, Operational
Devices: c20t0d0 c20t0d1 c20t0d2 c20t0d3 c20t0d4 c20t0d5 c20t0d6

TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 0 c20t0d0 6005-08B4-0010-1064-0000-B000-006D-0000 4
255/255/0/0.0
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQE04J no
c12t0d1 td0 no Active
c6t0d1 td1 no Available

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQF00E no
c4t0d1 td1 no Standby
c14t0d1 td0 no Standby


TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 1 c20t0d1 6005-08B4-0010-1064-0000-B000-0072-0000 4
255/255/0/0.1
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQE04J no
c12t0d2 td0 no Active
c6t0d2 td1 no Available

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQF00E no
c4t0d2 td1 no Standby
c14t0d2 td0 no Standby


TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 2 c20t0d2 6005-08B4-0010-1064-0000-B000-0075-0000 4
255/255/0/0.2
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQE04J no
c12t0d3 td0 no Active
c6t0d3 td1 no Available

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQF00E no
c4t0d3 td1 no Standby
c14t0d3 td0 no Standby


TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 3 c20t0d3 6005-08B4-0010-1064-0000-B000-007A-0000 4
255/255/0/0.3
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQE04J no
c12t0d4 td0 no Active
c6t0d4 td1 no Available

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQF00E no
c4t0d4 td1 no Standby
c14t0d4 td0 no Standby


TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 4 c20t0d4 6005-08B4-0010-1064-0000-B000-0081-0000 4
255/255/0/0.4
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQE04J no
c12t0d5 td0 no Active
c6t0d5 td1 no Available

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQF00E no
c4t0d5 td1 no Standby
c14t0d5 td0 no Standby


TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 5 c20t0d5 6005-08B4-0010-1064-0000-B000-0087-0000 4
255/255/0/0.5
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQE04J no
c12t0d6 td0 no Active
c6t0d6 td1 no Available

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQF00E no
c4t0d6 td1 no Standby
c14t0d6 td0 no Standby


TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 6 c20t0d6 6005-08B4-0010-1064-0000-B000-0084-0000 4
255/255/0/0.6
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQE04J no
c12t0d7 td0 no Active
c6t0d7 td1 no Available

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AAQF00E no
c4t0d7 td1 no Standby
c14t0d7 td0 no Standby

But now, after reboot, it's gone !
I have to reinstall it again before I can see the right paths...

Thanks!
0 Kudos
Dave Hutton
Honored Contributor

‎03-17-2005 06:52 AM

‎03-17-2005 06:52 AM

Re: Secure Path doesn't work after reboot

You read my mind. When you created your host on the eva did you select HPUX?
Its defined when you create a new host under operating type. Something like this happened to me when I added a new host. It think it defaults to "windows".

Dave

0 Kudos
Dave Hutton
Honored Contributor

‎03-17-2005 06:58 AM

‎03-17-2005 06:58 AM

Re: Secure Path doesn't work after reboot

I should also add, did you upgrade this version of Securepath to D? I know there's specific directions when upgrading. That you should vgexport and vgimport back in. I don't recall if it was going from 3.0A to 3.0D or if it was upgrading from any of the prior versions.

Anyway, I do know theres a section on upgrading Securepath in the manual.


0 Kudos
yyghp
Super Advisor

‎03-17-2005 07:11 AM

‎03-17-2005 07:11 AM

Re: Secure Path doesn't work after reboot

Hi Dave,

There is no option for the host to present from CommandViewEVA, I can't choose whether it's windows or hp-ux.

And the SP I installed is 3.0D.

I installed the same on other 2 servers but work fine there...
0 Kudos
Tim D Fulford
Honored Contributor

‎03-17-2005 07:52 AM

‎03-17-2005 07:52 AM

Re: Secure Path doesn't work after reboot

Hi

what happens when you do

# diskinfo /dev/rdsk/c18t0d0
(e.g. the "real" paths to the disks & not c20 which is the "virtual" path)

# tdutil td0
# tdutil td1
# fcmsutil -stat td0
# fcmsutil -stat td1

I'm wondering if, for some reason ALL the paths to the eva5000 has disappeared?

Regards

Tim
-
0 Kudos
yyghp
Super Advisor

‎03-17-2005 08:57 AM

‎03-17-2005 08:57 AM

Re: Secure Path doesn't work after reboot

# fcmsutil /dev/td0

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x0a0700
N_Port Node World Wide Name = 0x50060b00002564b7
N_Port Port World Wide Name = 0x50060b00002564b6
Driver state = ONLINE
Hardware Path is = 0/2/1/0
Number of Assisted IOs = 5918
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 (AR1204) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Oct 11 2004, 14:45:41

# fcmsutil /dev/td1

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x0b0700
N_Port Node World Wide Name = 0x50060b00002564bd
N_Port Port World Wide Name = 0x50060b00002564bc
Driver state = ONLINE
Hardware Path is = 0/5/2/0
Number of Assisted IOs = 5918
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 (AR1204) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Oct 11 2004, 14:45:41

And I chose two LUNs showed below:

# diskinfo /dev/rdsk/c12t0d1
SCSI describe of /dev/rdsk/c12t0d1:
vendor: COMPAQ
product id: HSV110 (C)COMPAQ
type: direct access
size: 104857600 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c14t0d7
SCSI describe of /dev/rdsk/c14t0d7:
vendor: COMPAQ
product id: HSV110 (C)COMPAQ
type: direct access
size: 419430400 Kbytes
bytes per sector: 512

Strange! The Only way I can make it work is to reinstall the SP, but after reboot, it will happen again :(
Thanks!
0 Kudos
yyghp
Super Advisor

‎03-17-2005 08:59 AM

‎03-17-2005 08:59 AM

Re: Secure Path doesn't work after reboot

It seems anything looks ok, until i reboot the server...

But i have another 2 boxes I installed half year ago with same version of SP, they worked fine from that time...

Thanks!
0 Kudos
yyghp
Super Advisor

‎03-18-2005 01:10 AM

‎03-18-2005 01:10 AM

Re: Secure Path doesn't work after reboot

should not have put the points that early, which makes experts here think the ticket has been closed.
0 Kudos
RolandH
Honored Contributor

‎03-18-2005 01:35 AM

‎03-18-2005 01:35 AM

Re: Secure Path doesn't work after reboot

Try this command

# spmgr add 5000-1FE1-5004-5690 -r all
# spmgr display

I have already taken the storage-id from your eva5000 so you can copy/paste the command into your terminal.

Roland
Sometimes you lose and sometimes the others win
0 Kudos
RolandH
Honored Contributor

‎03-18-2005 01:44 AM

‎03-18-2005 01:44 AM

Re: Secure Path doesn't work after reboot

Forgett that what I have written before.

Do this:

# spmgr add 5000-1FE1-5004-5690 -r all
# ioscan
# spmgr display



Roland
Sometimes you lose and sometimes the others win
0 Kudos
yyghp
Super Advisor

‎03-18-2005 03:12 AM

‎03-18-2005 03:12 AM

Re: Secure Path doesn't work after reboot

Thanks but

# spmgr add -r 5000-1FE1-5004-5690 all
No LUNs have been presented to Secure Path.

when it only happen after reboot ?
0 Kudos
yyghp
Super Advisor

‎03-18-2005 03:42 AM

‎03-18-2005 03:42 AM

Re: Secure Path doesn't work after reboot

up
0 Kudos
RolandH
Honored Contributor

‎03-18-2005 03:58 AM

‎03-18-2005 03:58 AM

Re: Secure Path doesn't work after reboot

What does your syslog say?

I have attached my output. I have a D Version, too.

Roland
Sometimes you lose and sometimes the others win
0 Kudos
yyghp
Super Advisor

‎03-18-2005 04:11 AM

‎03-18-2005 04:11 AM

Re: Secure Path doesn't work after reboot

I just check the syslog, it looks fine...
( please check the attachment )

Thanks!
0 Kudos
yyghp
Super Advisor

‎03-18-2005 04:14 AM

‎03-18-2005 04:14 AM

Re: Secure Path doesn't work after reboot

Oh, you are right, it doesn't have the message like yours:

Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D370000F00000530000 changed to Alive
Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D3700011000006A0000 changed to Alive
Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D3700011000007D0000 changed to Alive
Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D370001100000840000 changed to Alive
Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D3700011000008B0000 changed to Alive
Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D370001100000920000 changed to Alive
Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D370001100000990000 changed to Alive
Mar 7 15:23:40 myhost vmunix: CPQswsp: Availability for LUN 600508B400011D370001100000A00000 changed to Alive

There must be somethiing wrong here...
0 Kudos
yyghp
Super Advisor

‎03-18-2005 05:55 AM

‎03-18-2005 05:55 AM

Re: Secure Path doesn't work after reboot

Now I tried to reinstall the SP again, before reboot I got this from syslog:

Mar 18 13:43:39 SRS137 vmunix: NOTICE: modld: Module already loaded
Mar 18 13:43:39 SRS137 vmunix: 255/255 swspBus
Mar 18 13:43:56 SRS137 vmunix: 0/5/2/0.11.1.0.0.0.1 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/2/1/0.10.1.0.0.0.1 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/5/2/0.11.1.0.0.0.2 hsx
Mar 18 13:43:43 SRS137 vmunix: NOTICE: modld: Module already loaded
Mar 18 13:43:56 SRS137 above message repeats 2 times
Mar 18 13:43:56 SRS137 vmunix: 0/2/1/0.10.1.0.0.0.2 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/5/2/0.11.1.0.0.0.3 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/2/1/0.10.1.0.0.0.3 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/5/2/0.11.1.0.0.0.4 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/2/1/0.10.1.0.0.0.4 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/5/2/0.11.1.0.0.0.5 hsx
Mar 18 13:43:56 SRS137 vmunix: 0/2/1/0.10.1.0.0.0.5 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.1.0.0.0.6 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.1.0.0.0.6 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.1.0.0.0.7 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.1.0.0.0.7 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.2.0.0.0.1 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.2.0.0.0.1 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.2.0.0.0.2 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.2.0.0.0.2 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.2.0.0.0.3 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.2.0.0.0.3 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.2.0.0.0.4 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.2.0.0.0.4 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.2.0.0.0.5 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.2.0.0.0.5 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.2.0.0.0.6 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.2.0.0.0.6 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/5/2/0.11.2.0.0.0.7 hsx
Mar 18 13:44:00 SRS137 vmunix: 0/2/1/0.10.2.0.0.0.7 hsx
Mar 18 13:44:00 SRS137 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B000006D0000 chan
ged to Alive
Mar 18 13:44:00 SRS137 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B00000720000 chan
ged to Alive
Mar 18 13:44:00 SRS137 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B00000750000 chan
ged to Alive
Mar 18 13:44:00 SRS137 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B000007A0000 chan
ged to Alive
Mar 18 13:44:00 SRS137 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B00000810000 chan
ged to Alive
Mar 18 13:44:00 SRS137 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B00000870000 chan
ged to Alive
Mar 18 13:44:00 SRS137 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B00000840000 chan
ged to Alive
Mar 18 13:44:00 SRS137 vmunix: 255/255/0 swsp
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0 tgt
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0.0 sdisk
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0.1 sdisk
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0.2 sdisk
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0.3 sdisk
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0.4 sdisk
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0.5 sdisk
Mar 18 13:44:00 SRS137 vmunix: 255/255/0/0.6 sdisk
Mar 18 13:44:15 SRS137 spagent[5399]: Starting spagent.
0 Kudos
yyghp
Super Advisor

‎03-18-2005 07:12 AM

‎03-18-2005 07:12 AM

Re: Secure Path doesn't work after reboot


Something important:

# fcmsutil /dev/td0 get remote all

Target N_Port_id is = 0x090100
Target state = DVS_UNOPENED
Symbolic Name = HSV110 (C)COMPAQ - EVA5KE1 - CR04BB
Port Type = N_PORT
SLER Capable (supports Retry & TRID) = NO
Target Port World Wide Name = 0x50001fe15004544d
Target Node World Wide Name = 0x50001fe150045440

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 9 Version_Low: 9
BB_Credit: 0 Ciro: 1
Alt_BBcred: 1 Rxsz: 800
Conseq: ff RO_Bitmap: 1
Resolution: 0 EDTOV(ms): 0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------


Target N_Port_id is = 0x090200
Target state = DVS_UNOPENED
Symbolic Name = HSV110 (C)COMPAQ - EVA5KE1 - CR04BB
Port Type = N_PORT
SLER Capable (supports Retry & TRID) = NO
Target Port World Wide Name = 0x50001fe150045448
Target Node World Wide Name = 0x50001fe150045440

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 9 Version_Low: 9
BB_Credit: 0 Ciro: 1
Alt_BBcred: 1 Rxsz: 800
Conseq: ff RO_Bitmap: 1
Resolution: 0 EDTOV(ms): 0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------


Target N_Port_id is = 0x0a0100
Target state = DVS_UNOPENED
Symbolic Name = HSV110 (C)COMPAQ - EVA5KS1 - CR04BB
Port Type = N_PORT
SLER Capable (supports Retry & TRID) = NO
Target Port World Wide Name = 0x50001fe150045699
Target Node World Wide Name = 0x50001fe150045690

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 9 Version_Low: 9
BB_Credit: 0 Ciro: 1
Alt_BBcred: 1 Rxsz: 800
Conseq: ff RO_Bitmap: 1
Resolution: 0 EDTOV(ms): 0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------


Target N_Port_id is = 0x0a0200
Target state = DVS_UNOPENED
Symbolic Name = HSV110 (C)COMPAQ - EVA5KS1 - CR04BB
Port Type = N_PORT
SLER Capable (supports Retry & TRID) = NO
Target Port World Wide Name = 0x50001fe15004569c
Target Node World Wide Name = 0x50001fe150045690

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 9 Version_Low: 9
BB_Credit: 0 Ciro: 1
Alt_BBcred: 1 Rxsz: 800
Conseq: ff RO_Bitmap: 1
Resolution: 0 EDTOV(ms): 0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------

All Target state = DVS_UNOPENED...

0 Kudos
yyghp
Super Advisor

‎03-22-2005 01:31 AM

‎03-22-2005 01:31 AM

Re: Secure Path doesn't work after reboot

Patch issue:

Download latest Patch Set for Secure Path from ITRC: itrc.hp.com
» patch/firmware database ( link in the middle of the page )
» find HP-UX patches in a patch set ( link at the end of the page )
step 1: Select a patch set: SecurePath
step 2: Select hardware and OS: 800 11.11
step 3: Select a patch strategy: conservative
Search » “add to selected patch list »” button
Download all in one ZIP file.

Unzip it files under local desktop

Upload all files (PHKL_*, PHCO_*, create_depot_hp-ux_11 ) to /tmp/patches

Run the create_depot script as user "root". create_depot_hp-ux_11 must run on a 11.X system. The create_depot_hp-ux script unpacks the patches, and uses swcopy to create the /tmp/patches/depot directory.
# sh create_depot_hp-ux_11

( Optional: After the depot is created, remove the individual patches, .text, and .depot files. If you are creating more than one depot, rename the /tmp/patches/depot directory, and remove /tmp/patches/depot.psf. )

Installing the depot:
SAM, choose the Source Depot Path is "/tmp/patches/depot", you can see the “Patch Bundle”.
Mark it and i
0 Kudos
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.