HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: No Login at System Console
Operating System - HP-UX
1832547
Members
6241
Online
110043
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 08:12 PM
10-09-2003 08:12 PM
Re: No Login at System Console
Hello again,
just wanted to inform you about what happened meanwhile, in case anyone hasn't yet lost interest in this thread.
Michael,
actually the HP support engineer suggested to include KCODE should I still be able to spare the additional space.
Don't exactly know for what reason, but I trust them.
T.G.,
all the external disks (i.e. those apart from root/boot disks) are SAN disks which don't use the SCSI protocol but are connected via Fibre Channel (well, maybe the FCP is doing internally some sort of SCSI mapping? I don't know anything about the innards of low level HW protocols).
I don't know much about FC/SAN topology either, and take for granted what I am furnished with from our SAN admins (they are payed better than we Unix admins so I think their knowledge should corrolate/compensate ;-)
About the PV timeout issue.
I already got this Hitachi related ominous 180 sec value conveyed by our SAN admins a long time ago, and usually keep an eye on an appropiately set value whenever I include a new disk.
Let's check it anyway, I might have forgotten some disks.
Because the machine is a cluster node not all the VGs are currently activated on this box, thus the redirection of stderr below.
# pvdisplay $(vgdisplay -v /dev/vg[!0]* 2>/dev/null|awk '/PV Name/{print$NF}')|grep -e PV\ Name -e Timeout
PV Name /dev/dsk/c4t5d0
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t2d7
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t7d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c4t5d1
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t1d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c4t5d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d1
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d2
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d3
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d4
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d6
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d1
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d2
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d3
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d4
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c7t5d6
IO Timeout (Seconds) default
PV Name /dev/dsk/c7t5d7
IO Timeout (Seconds) default
PV Name /dev/dsk/c7t6d0
IO Timeout (Seconds) default
Ah, there must have slipped three disks which still use the default timeout.
I will check them separately.
just wanted to inform you about what happened meanwhile, in case anyone hasn't yet lost interest in this thread.
Michael,
actually the HP support engineer suggested to include KCODE should I still be able to spare the additional space.
Don't exactly know for what reason, but I trust them.
T.G.,
all the external disks (i.e. those apart from root/boot disks) are SAN disks which don't use the SCSI protocol but are connected via Fibre Channel (well, maybe the FCP is doing internally some sort of SCSI mapping? I don't know anything about the innards of low level HW protocols).
I don't know much about FC/SAN topology either, and take for granted what I am furnished with from our SAN admins (they are payed better than we Unix admins so I think their knowledge should corrolate/compensate ;-)
About the PV timeout issue.
I already got this Hitachi related ominous 180 sec value conveyed by our SAN admins a long time ago, and usually keep an eye on an appropiately set value whenever I include a new disk.
Let's check it anyway, I might have forgotten some disks.
Because the machine is a cluster node not all the VGs are currently activated on this box, thus the redirection of stderr below.
# pvdisplay $(vgdisplay -v /dev/vg[!0]* 2>/dev/null|awk '/PV Name/{print$NF}')|grep -e PV\ Name -e Timeout
PV Name /dev/dsk/c4t5d0
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t2d7
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t7d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c4t5d1
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t1d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c4t5d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d1
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d2
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d3
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d4
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t4d6
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d1
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d2
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d3
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d4
IO Timeout (Seconds) 180
PV Name /dev/dsk/c5t6d5
IO Timeout (Seconds) 180
PV Name /dev/dsk/c7t5d6
IO Timeout (Seconds) default
PV Name /dev/dsk/c7t5d7
IO Timeout (Seconds) default
PV Name /dev/dsk/c7t6d0
IO Timeout (Seconds) default
Ah, there must have slipped three disks which still use the default timeout.
I will check them separately.
Madness, thy name is system administration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 08:18 PM
10-09-2003 08:18 PM
Re: No Login at System Console
Sorry, this happens when one's replies get too long.
What happened?
This morning I received a call from the HP supporter who rightly said that I should have told him the whole truth (i.e. the POWERFAIL messages in syslog.log) in the beginning.
He also said that therefore, he transfers the call to a hardware colleague for closer inspection of possible HW issues, and who is more into STM.
What happened?
This morning I received a call from the HP supporter who rightly said that I should have told him the whole truth (i.e. the POWERFAIL messages in syslog.log) in the beginning.
He also said that therefore, he transfers the call to a hardware colleague for closer inspection of possible HW issues, and who is more into STM.
Madness, thy name is system administration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2003 12:39 AM
10-10-2003 12:39 AM
Re: No Login at System Console
Yes, I also missed the powerfail messages. This thread has certainly weaved around. Lets look at a couple of things beginning with these devices, all on controller 5:
vg[8]: pvnum=1 (dev_t=0x1f052700) is POWERFAILED
vg[8]: pvnum=2 (dev_t=0x1f057500) is POWERFAILED
vg[9]: pvnum=1 (dev_t=0x1f051500) is POWERFAILED
vg[10]: pvnum=0 (dev_t=0x1f056100) is POWERFAILED
vg[10]: pvnum=1 (dev_t=0x1f056200) is POWERFAILED
vg[10]: pvnum=2 (dev_t=0x1f056300) is POWERFAILED
vg[10]: pvnum=3 (dev_t=0x1f056400) is POWERFAILED
vg[10]: pvnum=4 (dev_t=0x1f056500) is POWERFAILED
vg[11]: pvnum=0 (dev_t=0x1f054100) is POWERFAILED
vg[11]: pvnum=1 (dev_t=0x1f054200) is POWERFAILED
vg[11]: pvnum=2 (dev_t=0x1f054300) is POWERFAILED
vg[11]: pvnum=3 (dev_t=0x1f054400) is POWERFAILED
vg[11]: pvnum=4 (dev_t=0x1f054500) is POWERFAILED
vg[11]: pvnum=5 (dev_t=0x1f054600) is POWERFAILED
############################################
Now lets id controller 5 which should be a fc HBA:
# ioscan -fnkC disk
# ioscan -fnkC fc
############################################
Finally, HP CE rely heavily on LOGTOOL so lets get the info ready for them.
STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY
############################################
Since everyone's gone this far DON'T EVEN THINK ABOUT NOT SHARING THIS INFORMATION. (* PLEASE ATTACH *)
Thanks!
vg[8]: pvnum=1 (dev_t=0x1f052700) is POWERFAILED
vg[8]: pvnum=2 (dev_t=0x1f057500) is POWERFAILED
vg[9]: pvnum=1 (dev_t=0x1f051500) is POWERFAILED
vg[10]: pvnum=0 (dev_t=0x1f056100) is POWERFAILED
vg[10]: pvnum=1 (dev_t=0x1f056200) is POWERFAILED
vg[10]: pvnum=2 (dev_t=0x1f056300) is POWERFAILED
vg[10]: pvnum=3 (dev_t=0x1f056400) is POWERFAILED
vg[10]: pvnum=4 (dev_t=0x1f056500) is POWERFAILED
vg[11]: pvnum=0 (dev_t=0x1f054100) is POWERFAILED
vg[11]: pvnum=1 (dev_t=0x1f054200) is POWERFAILED
vg[11]: pvnum=2 (dev_t=0x1f054300) is POWERFAILED
vg[11]: pvnum=3 (dev_t=0x1f054400) is POWERFAILED
vg[11]: pvnum=4 (dev_t=0x1f054500) is POWERFAILED
vg[11]: pvnum=5 (dev_t=0x1f054600) is POWERFAILED
############################################
Now lets id controller 5 which should be a fc HBA:
# ioscan -fnkC disk
# ioscan -fnkC fc
############################################
Finally, HP CE rely heavily on LOGTOOL so lets get the info ready for them.
STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY
############################################
Since everyone's gone this far DON'T EVEN THINK ABOUT NOT SHARING THIS INFORMATION. (* PLEASE ATTACH *)
Thanks!
Support Fatherhood - Stop Family Law
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2003 01:21 AM
10-10-2003 01:21 AM
Re: No Login at System Console
Michael,
thanks for staying with this thread.
I could not respond earlier since I had to accompany instellation of new servers (that operate on Solaris).
Now I'm back and Friday afternoon's weekend signs are drawing near (viz. knocking off sources of disturbance aka colleagues and customers).
Now to the info you requested.
These are the busses
# ioscan -knfCext_bus
Class I H/W Path Driver S/W State H/W Type Description
================================================================================
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Fast Wide Single-Ended
ext_bus 1 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 2 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
ext_bus 3 0/4/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
ext_bus 6 0/4/0/0.8.0.255.1 fcpdev CLAIMED INTERFACE FCP Device Interface
ext_bus 7 1/0/0/0.98.13.19.0 fcparray CLAIMED INTERFACE FCP Array Interface
ext_bus 9 1/0/0/0.98.13.255.1 fcpdev CLAIMED INTERFACE FCP Device Interface
ext_bus 4 1/10/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
How did you evaluate it was controller 5?
All I can see is that the hex addresses all start (or rather end, if you read it from right to left) with the sequence 1f05.
Would you mind revealing the mapping to me?
Trusting your wisdom I take 5 for granted, and restrict further output on this bus.
As you can see it's of driver fcparray.
It's just funny to see how lsdev doesn't know this driver
# lsdev -d fcparray
Character Block Driver Class
Never mind, at least ioscan can live with it.
# ioscan -knfdfcparray
Class I H/W Path Driver S/W State H/W Type Description
===============================================================================
ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
ext_bus 7 1/0/0/0.98.13.19.0 fcparray CLAIMED INTERFACE FCP Array Interface
This is reported as being of class fc
# lsdev -Cfc
Character Block Driver Class
241 -1 td fc
# ioscan -kfCfc
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/4/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
fc 4 1/0/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapte
r
fc 2 1/2/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapte
r
fc 1 1/10/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
As you can see, no bus 5 here.
Instead of dumping all the disks below you may find the list of disks that are attached to the HW path of bus 5.
In the attachment you may find the logtool dump for the command sequence you requested.
Class I H/W Path Driver S/W State H/W Type Description
=================================================================================
ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 25 0/4/0/0.8.0.16.0.0 tgt CLAIMED DEVICE
disk 25 0/4/0/0.8.0.16.0.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 26 0/4/0/0.8.0.16.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d1 /dev/rdsk/c5t0d1
disk 27 0/4/0/0.8.0.16.0.0.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d2 /dev/rdsk/c5t0d2
disk 28 0/4/0/0.8.0.16.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d3 /dev/rdsk/c5t0d3
disk 29 0/4/0/0.8.0.16.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d4 /dev/rdsk/c5t0d4
disk 30 0/4/0/0.8.0.16.0.0.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d5 /dev/rdsk/c5t0d5
disk 31 0/4/0/0.8.0.16.0.0.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d6 /dev/rdsk/c5t0d6
disk 32 0/4/0/0.8.0.16.0.0.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d7 /dev/rdsk/c5t0d7
target 26 0/4/0/0.8.0.16.0.1 tgt CLAIMED DEVICE
disk 33 0/4/0/0.8.0.16.0.1.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
disk 34 0/4/0/0.8.0.16.0.1.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d1 /dev/rdsk/c5t1d1
disk 35 0/4/0/0.8.0.16.0.1.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d2 /dev/rdsk/c5t1d2
disk 36 0/4/0/0.8.0.16.0.1.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d3 /dev/rdsk/c5t1d3
disk 37 0/4/0/0.8.0.16.0.1.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d4 /dev/rdsk/c5t1d4
disk 38 0/4/0/0.8.0.16.0.1.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d5 /dev/rdsk/c5t1d5
disk 39 0/4/0/0.8.0.16.0.1.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d6 /dev/rdsk/c5t1d6
disk 40 0/4/0/0.8.0.16.0.1.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d7 /dev/rdsk/c5t1d7
target 27 0/4/0/0.8.0.16.0.2 tgt CLAIMED DEVICE
disk 11 0/4/0/0.8.0.16.0.2.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
disk 12 0/4/0/0.8.0.16.0.2.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d1 /dev/rdsk/c5t2d1
disk 13 0/4/0/0.8.0.16.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d2 /dev/rdsk/c5t2d2
disk 14 0/4/0/0.8.0.16.0.2.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d3 /dev/rdsk/c5t2d3
disk 15 0/4/0/0.8.0.16.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d4 /dev/rdsk/c5t2d4
disk 16 0/4/0/0.8.0.16.0.2.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d5 /dev/rdsk/c5t2d5
disk 17 0/4/0/0.8.0.16.0.2.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d6 /dev/rdsk/c5t2d6
disk 41 0/4/0/0.8.0.16.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d7 /dev/rdsk/c5t2d7
target 28 0/4/0/0.8.0.16.0.3 tgt CLAIMED DEVICE
disk 42 0/4/0/0.8.0.16.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d0 /dev/rdsk/c5t3d0
disk 43 0/4/0/0.8.0.16.0.3.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d1 /dev/rdsk/c5t3d1
disk 44 0/4/0/0.8.0.16.0.3.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d2 /dev/rdsk/c5t3d2
disk 45 0/4/0/0.8.0.16.0.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d3 /dev/rdsk/c5t3d3
disk 46 0/4/0/0.8.0.16.0.3.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d4 /dev/rdsk/c5t3d4
disk 47 0/4/0/0.8.0.16.0.3.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d5 /dev/rdsk/c5t3d5
disk 48 0/4/0/0.8.0.16.0.3.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d6 /dev/rdsk/c5t3d6
disk 49 0/4/0/0.8.0.16.0.3.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d7 /dev/rdsk/c5t3d7
target 29 0/4/0/0.8.0.16.0.4 tgt CLAIMED DEVICE
disk 50 0/4/0/0.8.0.16.0.4.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0
disk 51 0/4/0/0.8.0.16.0.4.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d1 /dev/rdsk/c5t4d1
disk 52 0/4/0/0.8.0.16.0.4.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d2 /dev/rdsk/c5t4d2
disk 53 0/4/0/0.8.0.16.0.4.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d3 /dev/rdsk/c5t4d3
disk 54 0/4/0/0.8.0.16.0.4.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d4 /dev/rdsk/c5t4d4
disk 55 0/4/0/0.8.0.16.0.4.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d5 /dev/rdsk/c5t4d5
disk 56 0/4/0/0.8.0.16.0.4.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d6 /dev/rdsk/c5t4d6
disk 57 0/4/0/0.8.0.16.0.4.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d7 /dev/rdsk/c5t4d7
target 30 0/4/0/0.8.0.16.0.5 tgt CLAIMED DEVICE
disk 58 0/4/0/0.8.0.16.0.5.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d0 /dev/rdsk/c5t5d0
disk 59 0/4/0/0.8.0.16.0.5.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d1 /dev/rdsk/c5t5d1
disk 60 0/4/0/0.8.0.16.0.5.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d2 /dev/rdsk/c5t5d2
disk 61 0/4/0/0.8.0.16.0.5.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d3 /dev/rdsk/c5t5d3
disk 62 0/4/0/0.8.0.16.0.5.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d4 /dev/rdsk/c5t5d4
disk 63 0/4/0/0.8.0.16.0.5.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d5 /dev/rdsk/c5t5d5
disk 64 0/4/0/0.8.0.16.0.5.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d6 /dev/rdsk/c5t5d6
disk 65 0/4/0/0.8.0.16.0.5.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d7 /dev/rdsk/c5t5d7
target 31 0/4/0/0.8.0.16.0.6 tgt CLAIMED DEVICE
disk 66 0/4/0/0.8.0.16.0.6.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d0 /dev/rdsk/c5t6d0
disk 67 0/4/0/0.8.0.16.0.6.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d1 /dev/rdsk/c5t6d1
disk 68 0/4/0/0.8.0.16.0.6.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d2 /dev/rdsk/c5t6d2
disk 69 0/4/0/0.8.0.16.0.6.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d3 /dev/rdsk/c5t6d3
disk 70 0/4/0/0.8.0.16.0.6.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d4 /dev/rdsk/c5t6d4
disk 71 0/4/0/0.8.0.16.0.6.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d5 /dev/rdsk/c5t6d5
disk 73 0/4/0/0.8.0.16.0.6.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d6 /dev/rdsk/c5t6d6
disk 74 0/4/0/0.8.0.16.0.6.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d7 /dev/rdsk/c5t6d7
target 32 0/4/0/0.8.0.16.0.7 tgt CLAIMED DEVICE
disk 75 0/4/0/0.8.0.16.0.7.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d0 /dev/rdsk/c5t7d0
disk 72 0/4/0/0.8.0.16.0.7.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d1 /dev/rdsk/c5t7d1
disk 76 0/4/0/0.8.0.16.0.7.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d2 /dev/rdsk/c5t7d2
disk 77 0/4/0/0.8.0.16.0.7.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d3 /dev/rdsk/c5t7d3
disk 78 0/4/0/0.8.0.16.0.7.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d4 /dev/rdsk/c5t7d4
disk 79 0/4/0/0.8.0.16.0.7.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d5 /dev/rdsk/c5t7d5
disk 80 0/4/0/0.8.0.16.0.7.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d6 /dev/rdsk/c5t7d6
Logtool Utility: View Raw Summary
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- Logtool Utility: View Raw Summary --
Summary of: /var/stm/logs/os/log10.raw.cur
Date/time of first entry: Wed Oct 8 03:56:12 2003
Date/time of last entry: Wed Oct 8 06:09:58 2003
Number of LPMC entries: 0
Number of System Overtemp entries: 0
Number of LVM entries: 0
Number of Logger Event entries: 0
Number of I/O Error entries: 74
Device paths for which entries exist:
(74) 0/4/0/0.8
Products for which entries exist:
(74) Fibre Channel Driver
Product Qualifiers for which entries exist:
(74) Mass_Storage
Logger Events for which entries exist:
(74) fcp
thanks for staying with this thread.
I could not respond earlier since I had to accompany instellation of new servers (that operate on Solaris).
Now I'm back and Friday afternoon's weekend signs are drawing near (viz. knocking off sources of disturbance aka colleagues and customers).
Now to the info you requested.
These are the busses
# ioscan -knfCext_bus
Class I H/W Path Driver S/W State H/W Type Description
================================================================================
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Fast Wide Single-Ended
ext_bus 1 0/0/2/0 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 2 0/0/2/1 c720 CLAIMED INTERFACE SCSI C875 Ultra Wide Single-Ended
ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
ext_bus 3 0/4/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
ext_bus 6 0/4/0/0.8.0.255.1 fcpdev CLAIMED INTERFACE FCP Device Interface
ext_bus 7 1/0/0/0.98.13.19.0 fcparray CLAIMED INTERFACE FCP Array Interface
ext_bus 9 1/0/0/0.98.13.255.1 fcpdev CLAIMED INTERFACE FCP Device Interface
ext_bus 4 1/10/0/0.8.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
How did you evaluate it was controller 5?
All I can see is that the hex addresses all start (or rather end, if you read it from right to left) with the sequence 1f05.
Would you mind revealing the mapping to me?
Trusting your wisdom I take 5 for granted, and restrict further output on this bus.
As you can see it's of driver fcparray.
It's just funny to see how lsdev doesn't know this driver
# lsdev -d fcparray
Character Block Driver Class
Never mind, at least ioscan can live with it.
# ioscan -knfdfcparray
Class I H/W Path Driver S/W State H/W Type Description
===============================================================================
ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
ext_bus 7 1/0/0/0.98.13.19.0 fcparray CLAIMED INTERFACE FCP Array Interface
This is reported as being of class fc
# lsdev -Cfc
Character Block Driver Class
241 -1 td fc
# ioscan -kfCfc
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/4/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
fc 4 1/0/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapte
r
fc 2 1/2/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapte
r
fc 1 1/10/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
As you can see, no bus 5 here.
Instead of dumping all the disks below you may find the list of disks that are attached to the HW path of bus 5.
In the attachment you may find the logtool dump for the command sequence you requested.
Class I H/W Path Driver S/W State H/W Type Description
=================================================================================
ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 25 0/4/0/0.8.0.16.0.0 tgt CLAIMED DEVICE
disk 25 0/4/0/0.8.0.16.0.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 26 0/4/0/0.8.0.16.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d1 /dev/rdsk/c5t0d1
disk 27 0/4/0/0.8.0.16.0.0.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d2 /dev/rdsk/c5t0d2
disk 28 0/4/0/0.8.0.16.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d3 /dev/rdsk/c5t0d3
disk 29 0/4/0/0.8.0.16.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d4 /dev/rdsk/c5t0d4
disk 30 0/4/0/0.8.0.16.0.0.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d5 /dev/rdsk/c5t0d5
disk 31 0/4/0/0.8.0.16.0.0.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d6 /dev/rdsk/c5t0d6
disk 32 0/4/0/0.8.0.16.0.0.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t0d7 /dev/rdsk/c5t0d7
target 26 0/4/0/0.8.0.16.0.1 tgt CLAIMED DEVICE
disk 33 0/4/0/0.8.0.16.0.1.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
disk 34 0/4/0/0.8.0.16.0.1.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d1 /dev/rdsk/c5t1d1
disk 35 0/4/0/0.8.0.16.0.1.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d2 /dev/rdsk/c5t1d2
disk 36 0/4/0/0.8.0.16.0.1.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d3 /dev/rdsk/c5t1d3
disk 37 0/4/0/0.8.0.16.0.1.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d4 /dev/rdsk/c5t1d4
disk 38 0/4/0/0.8.0.16.0.1.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d5 /dev/rdsk/c5t1d5
disk 39 0/4/0/0.8.0.16.0.1.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d6 /dev/rdsk/c5t1d6
disk 40 0/4/0/0.8.0.16.0.1.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t1d7 /dev/rdsk/c5t1d7
target 27 0/4/0/0.8.0.16.0.2 tgt CLAIMED DEVICE
disk 11 0/4/0/0.8.0.16.0.2.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
disk 12 0/4/0/0.8.0.16.0.2.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d1 /dev/rdsk/c5t2d1
disk 13 0/4/0/0.8.0.16.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d2 /dev/rdsk/c5t2d2
disk 14 0/4/0/0.8.0.16.0.2.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d3 /dev/rdsk/c5t2d3
disk 15 0/4/0/0.8.0.16.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d4 /dev/rdsk/c5t2d4
disk 16 0/4/0/0.8.0.16.0.2.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d5 /dev/rdsk/c5t2d5
disk 17 0/4/0/0.8.0.16.0.2.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d6 /dev/rdsk/c5t2d6
disk 41 0/4/0/0.8.0.16.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t2d7 /dev/rdsk/c5t2d7
target 28 0/4/0/0.8.0.16.0.3 tgt CLAIMED DEVICE
disk 42 0/4/0/0.8.0.16.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d0 /dev/rdsk/c5t3d0
disk 43 0/4/0/0.8.0.16.0.3.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d1 /dev/rdsk/c5t3d1
disk 44 0/4/0/0.8.0.16.0.3.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d2 /dev/rdsk/c5t3d2
disk 45 0/4/0/0.8.0.16.0.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d3 /dev/rdsk/c5t3d3
disk 46 0/4/0/0.8.0.16.0.3.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d4 /dev/rdsk/c5t3d4
disk 47 0/4/0/0.8.0.16.0.3.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d5 /dev/rdsk/c5t3d5
disk 48 0/4/0/0.8.0.16.0.3.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d6 /dev/rdsk/c5t3d6
disk 49 0/4/0/0.8.0.16.0.3.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t3d7 /dev/rdsk/c5t3d7
target 29 0/4/0/0.8.0.16.0.4 tgt CLAIMED DEVICE
disk 50 0/4/0/0.8.0.16.0.4.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0
disk 51 0/4/0/0.8.0.16.0.4.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d1 /dev/rdsk/c5t4d1
disk 52 0/4/0/0.8.0.16.0.4.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d2 /dev/rdsk/c5t4d2
disk 53 0/4/0/0.8.0.16.0.4.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d3 /dev/rdsk/c5t4d3
disk 54 0/4/0/0.8.0.16.0.4.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d4 /dev/rdsk/c5t4d4
disk 55 0/4/0/0.8.0.16.0.4.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d5 /dev/rdsk/c5t4d5
disk 56 0/4/0/0.8.0.16.0.4.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d6 /dev/rdsk/c5t4d6
disk 57 0/4/0/0.8.0.16.0.4.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t4d7 /dev/rdsk/c5t4d7
target 30 0/4/0/0.8.0.16.0.5 tgt CLAIMED DEVICE
disk 58 0/4/0/0.8.0.16.0.5.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d0 /dev/rdsk/c5t5d0
disk 59 0/4/0/0.8.0.16.0.5.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d1 /dev/rdsk/c5t5d1
disk 60 0/4/0/0.8.0.16.0.5.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d2 /dev/rdsk/c5t5d2
disk 61 0/4/0/0.8.0.16.0.5.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d3 /dev/rdsk/c5t5d3
disk 62 0/4/0/0.8.0.16.0.5.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d4 /dev/rdsk/c5t5d4
disk 63 0/4/0/0.8.0.16.0.5.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d5 /dev/rdsk/c5t5d5
disk 64 0/4/0/0.8.0.16.0.5.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d6 /dev/rdsk/c5t5d6
disk 65 0/4/0/0.8.0.16.0.5.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t5d7 /dev/rdsk/c5t5d7
target 31 0/4/0/0.8.0.16.0.6 tgt CLAIMED DEVICE
disk 66 0/4/0/0.8.0.16.0.6.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d0 /dev/rdsk/c5t6d0
disk 67 0/4/0/0.8.0.16.0.6.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d1 /dev/rdsk/c5t6d1
disk 68 0/4/0/0.8.0.16.0.6.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d2 /dev/rdsk/c5t6d2
disk 69 0/4/0/0.8.0.16.0.6.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d3 /dev/rdsk/c5t6d3
disk 70 0/4/0/0.8.0.16.0.6.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d4 /dev/rdsk/c5t6d4
disk 71 0/4/0/0.8.0.16.0.6.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d5 /dev/rdsk/c5t6d5
disk 73 0/4/0/0.8.0.16.0.6.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d6 /dev/rdsk/c5t6d6
disk 74 0/4/0/0.8.0.16.0.6.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t6d7 /dev/rdsk/c5t6d7
target 32 0/4/0/0.8.0.16.0.7 tgt CLAIMED DEVICE
disk 75 0/4/0/0.8.0.16.0.7.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d0 /dev/rdsk/c5t7d0
disk 72 0/4/0/0.8.0.16.0.7.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d1 /dev/rdsk/c5t7d1
disk 76 0/4/0/0.8.0.16.0.7.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d2 /dev/rdsk/c5t7d2
disk 77 0/4/0/0.8.0.16.0.7.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d3 /dev/rdsk/c5t7d3
disk 78 0/4/0/0.8.0.16.0.7.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d4 /dev/rdsk/c5t7d4
disk 79 0/4/0/0.8.0.16.0.7.5 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d5 /dev/rdsk/c5t7d5
disk 80 0/4/0/0.8.0.16.0.7.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c5t7d6 /dev/rdsk/c5t7d6
Logtool Utility: View Raw Summary
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- Logtool Utility: View Raw Summary --
Summary of: /var/stm/logs/os/log10.raw.cur
Date/time of first entry: Wed Oct 8 03:56:12 2003
Date/time of last entry: Wed Oct 8 06:09:58 2003
Number of LPMC entries: 0
Number of System Overtemp entries: 0
Number of LVM entries: 0
Number of Logger Event entries: 0
Number of I/O Error entries: 74
Device paths for which entries exist:
(74) 0/4/0/0.8
Products for which entries exist:
(74) Fibre Channel Driver
Product Qualifiers for which entries exist:
(74) Mass_Storage
Logger Events for which entries exist:
(74) fcp
Madness, thy name is system administration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2003 03:56 AM
10-10-2003 03:56 AM
Re: No Login at System Console
First question first â â ¦How did you evaluate it was controller 5?...â
Note: dev_t=0x1f052700 translates to c5t2d7.
And here is c4t2d7 on HW path 0/4/0/0.8.0.16.0.2.7 :
# disk 41 0/4/0/0.8.0.16.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
# /dev/dsk/c5t2d7 /dev/rdsk/c5t2d7
- Note â â ¦ext_bus 5â ¦â in your command. 5 is c5.
# ioscan -knfCext_bus
# ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
###########################################################
- Note the same HW path â â ¦0/4/0/0.8.0.16.0â ¦â in
# ioscan -kfCfc
# fc 0 0/4/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
###########################################################
# Walk down HW path 0/4/0/0
# ioscan â fnkH 0/4/0/0
###########################################################
Finally, LOGTOOL confirms 74 errors on 0/4/0/0.8 in 3 hours. Iâ d say you got a HW failure in progress and can probably take this to HP HW support.
Logtool Utility: View Raw Summary
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- Logtool Utility: View Raw Summary --
Date/time of first entry: Wed Oct 8 03:56:12 2003
Date/time of last entry: Wed Oct 8 06:09:58 2003
Number of I/O Error entries: 74
Device paths for which entries exist:
(74) 0/4/0/0.8
Products for which entries exist:
(74) Fibre Channel Driver
Product Qualifiers for which entries exist:
(74) Mass_Storage
Logger Events for which entries exist:
(74) fcp
###########################################################
What exactly is â â ¦0
Note: dev_t=0x1f052700 translates to c5t2d7.
And here is c4t2d7 on HW path 0/4/0/0.8.0.16.0.2.7 :
# disk 41 0/4/0/0.8.0.16.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
# /dev/dsk/c5t2d7 /dev/rdsk/c5t2d7
- Note â â ¦ext_bus 5â ¦â in your command. 5 is c5.
# ioscan -knfCext_bus
# ext_bus 5 0/4/0/0.8.0.16.0 fcparray CLAIMED INTERFACE FCP Array Interface
###########################################################
- Note the same HW path â â ¦0/4/0/0.8.0.16.0â ¦â in
# ioscan -kfCfc
# fc 0 0/4/0/0 fcT1 CLAIMED INTERFACE HP Fibre Channel Mass Storage Adapter
###########################################################
# Walk down HW path 0/4/0/0
# ioscan â fnkH 0/4/0/0
###########################################################
Finally, LOGTOOL confirms 74 errors on 0/4/0/0.8 in 3 hours. Iâ d say you got a HW failure in progress and can probably take this to HP HW support.
Logtool Utility: View Raw Summary
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-- Logtool Utility: View Raw Summary --
Date/time of first entry: Wed Oct 8 03:56:12 2003
Date/time of last entry: Wed Oct 8 06:09:58 2003
Number of I/O Error entries: 74
Device paths for which entries exist:
(74) 0/4/0/0.8
Products for which entries exist:
(74) Fibre Channel Driver
Product Qualifiers for which entries exist:
(74) Mass_Storage
Logger Events for which entries exist:
(74) fcp
###########################################################
What exactly is â â ¦0
Support Fatherhood - Stop Family Law
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2003 03:59 AM
10-10-2003 03:59 AM
Re: No Login at System Console
Man this is bad:
(74) 0/4/0/0.8
This is your bad device HW path.
ioscan -fnkH 0/4/0/0.8
(74) 0/4/0/0.8
This is your bad device HW path.
ioscan -fnkH 0/4/0/0.8
Support Fatherhood - Stop Family Law
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2003 07:06 PM
10-12-2003 07:06 PM
Re: No Login at System Console
Micheal,
I really must have been sitting on my eyes (can one put it this way in English? btw in German we have a saying which literally translated would go "to have tomatoes on one's eyes").
Of course, I should have been able to work it out on my own how the dev_t nomenclature is to be read.
On the other hand I already knew that the controller No. e.g. c5 refers to the HW path at ext_bus whose ID equals 5.
This was the dump of all the c5* disks from ioscan I posted which actually was the output from
"ioscan -knf -H 0/4/0/0.8.0.16.0"
I simply forgot to copy and paste the command line itself in the posting, while the rest (i.e. the output) was piped into mailx.
Thank you for your interpretation of the logtool output.
As I wrote, the case already had been transferred to an HP Support HW SE.
If he/she comes up with a solution I will tell you here.
But first I eagerly await their call, mail etc.
I really must have been sitting on my eyes (can one put it this way in English? btw in German we have a saying which literally translated would go "to have tomatoes on one's eyes").
Of course, I should have been able to work it out on my own how the dev_t nomenclature is to be read.
On the other hand I already knew that the controller No. e.g. c5 refers to the HW path at ext_bus whose ID equals 5.
This was the dump of all the c5* disks from ioscan I posted which actually was the output from
"ioscan -knf -H 0/4/0/0.8.0.16.0"
I simply forgot to copy and paste the command line itself in the posting, while the rest (i.e. the output) was piped into mailx.
Thank you for your interpretation of the logtool output.
As I wrote, the case already had been transferred to an HP Support HW SE.
If he/she comes up with a solution I will tell you here.
But first I eagerly await their call, mail etc.
Madness, thy name is system administration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2003 09:10 PM
10-12-2003 09:10 PM
Re: No Login at System Console
Just a question: have you asked EMC to check for errors on the Host Bus Adapters?
I assume that you are using PVlinks?
I assume that you are using PVlinks?
Trying is the first step to failure - Homer Simpson
- « Previous
-
- 1
- 2
- Next »
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP