[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::ase

Title:ase
Moderator:SMURF::GROSSO
Created:Thu Jul 29 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2114
Total number of notes:7347

1863.0. "How to find the SCSI ID of a controller on a running system?" by VIRGIN::SUTTER (Who are you ??? - I'm BATMAN !!!) Thu Feb 06 1997 05:26

Hello, 

the question that came up today was this: 

"How do you find the SCSI-ID (target) of the local KZPSA if you don't 
want to bring the system to console mode?" 

We had the case that the KZPSA in a system beeing part of an ASE Cluster
broke down and had to be replaced. We did not know how to set the ID on 
the replaced KZPSA since we did not know what the ID was set to on the 
remaining, (available!) system. 

We only had 1 shared SCSI-Bus ... 

Any ideas? 

Thank's & Regards, 

Arnold & TRUST
T.RTitleUserPersonal
Name		DateLines
1863.1use the file commandDYOSW5::WILDERDoes virtual reality get swapped?Thu Feb 06 1997 07:025
    file /dev/rrz*c
    This will show, among other things, the bus number the disk is on.
    
    /jim
1863.2... does not show what I'm looking for ...VIRGIN::SUTTERWho are you ??? - I'm BATMAN !!!Thu Feb 06 1997 07:376
>     file /dev/rrz*c
>    This will show, among other things, the bus number the disk is on.

What I'm looking for is the SCSI-ID of the controller, not the disk.
SCSI-Controller on shared buses need to be on different target ID's.
1863.3KITCHE::schottEric R. Schott USG Product ManagementThu Feb 06 1997 07:4013
The boot messages are in UERF (DECevent) and in /var/adm/messages

Have you run sys_check?  It should find the boot message..

http://www-unix.zk3.dec.com/tuning/tools/sys_check/sys_check.html


Also, I think with V1.4, clu_ivp should find this also...

regards

Eric
1863.4sys_check even makes coffee?-)VIRGIN::SUTTERWho are you ??? - I'm BATMAN !!!Thu Feb 06 1997 08:0018
'clu_ivp -v' does not produce what I'm looking for. 

# grep found /var/adm/messages 

does give me some kernel messages where in the past the other systems
did have it's SCSI-ID's on a certain bus in the past. 

Now if you have 3 or more members, it probably can be extrapolated 
by comparing the output of above command on all members what SCSI-ID the 
system had that is down and has a broken KZPSA. 

What I was looking for is some way to find out what ID the OWN KZPSA
had on a running system but I suppose above workaround does it as well. 

Regards, 

Arnold
P.S.: The cluster map may also lead to the proper ID if one exists...
1863.5Some help ??JANIX::jmhsendmail: The Vietnam of BerkeleyThu Feb 06 1997 10:5814
>>Notefile: SMURF::ASE
>>Note: 1863.4
>>Author: VIRGIN::SUTTER "Who are you ??? - I'm BATMAN !!!"
>>Topic: How to find the SCSI ID of a controller on a running system?
>>Title: sys_check even makes coffee?-)


	Does "# scu show edt lun 0 |grep Processor" help ??
	on the remote/local system help (this should give you
	an idea which SCSI IDs have been assigned to the KZPSAs
	(assuming you use unique IDs on all nodes ...)) .

 - Jan
1863.6Use scu show path inquirySMURF::KNIGHTFred KnightMon Feb 10 1997 10:4214
Everything so far suggest guessing the host ID based on the
other IDs on the bus.  What was really asked for was the host
ID of the adapter itself.  That is returned in the CAM path
inquiry data.

# scu
scu> set nexus bus n
scu> show path inquiry
<....>
SCSI Device ID of Initiator:  7
<....>
scu>

	Fred