From: manoj ghag (manojghag@rediffmail.com)
Date: Tue Jun 01 2004 - 05:08:19 EDT
Hi ,
I am facing a problem in getting D1000 Storage shared between the two
sun server
So I got a proper responce from sun managers .. thank you very
much for that ........
But while doing that I have faced problem...
I mean I
don't knwo what ID I need to change ??
Please check my steps ..am i doing any
wrong thing .. please reply me
I am confused in this step
1 cd
/sbus@1f,0/SUNW,fas@2,8800000
4 cd /sbus@1f,0/SUNW,fas@0,8800000
What should
be this in my case ???
Please tell me
-----------------------------------------------------------------------------
----------
FAQ ID Synopsis Date
3174 How to change scsi-initiator-id
effectively 14 Jun 2000
-----------------------------------------------------------------------------
----------
1) This is a better solution because it only changes the
initiator-id on the
adapters that need to be changed. The CD-ROM remains
functional after the
change.
Go to the OpenBoot prompt and follow the steps
accordingly:
### These steps to find out relavant adapters' paths:
ok set
NVRAM auto-boot? false
ok reset-all
ok probe-scsi-all
### These steps to edit
the nvramrc script, to run
### at bootup, to change the scsi-initiator-id:
ok
nvedit
0 probe-all
1 cd /sbus@1f,0/SUNW,fas@2,8800000
2 6 encode-int
" scsi-initiator-id" property
3 device-end
4 cd
/sbus@1f,0/SUNW,fas@0,8800000
5 6 encode-int " scsi-initiator-id" property
6 device-end
7 install-console
8 banner
<CTRL-C>
ok nvstore
ok setenv
use-nvramrc? true
ok reset-all
NOTE:
At step 1 and 4, the paths were taken
from "ok probe-scsi-all".
At step 2 and 5, there is a white space between the
first (") and scsi.
Remember also to save the nvramrc script by executing
"nvstore"
and set to use nvramrc script at bootup by executing "setenv
use-nvramrc? true"
-----------------------------------------------------------------------------
-----------------------------------------
My SCSI Informations is as follows
(As per the DOC we need to do cd /sbus@1f,0/SUNW,fas@2,8800000 But I don't
have anything like that in my server :( How should I go about)
?????????
-----------------------------------------------------------------------------
------------------------------------------
Node 0xf002ce38
net:
'/pci@1f,4000/network@1,1'
disk: '/pci@1f,4000/scsi@3/disk@0,0'
cdrom: '/pci@1f,4000/scsi@3/disk@6,0:f'
tape:
'/pci@1f,4000/scsi@3,1/tape@4,0'
tape1:
'/pci@1f,4000/scsi@3,1/tape@5,0'
tape0:
'/pci@1f,4000/scsi@3,1/tape@4,0'
disk6:
'/pci@1f,4000/scsi@3/disk@6,0'
disk5: '/pci@1f,4000/scsi@3/disk@5,0'
disk4: '/pci@1f,4000/scsi@3/disk@4,0'
disk3:
'/pci@1f,4000/scsi@3/disk@3,0'
disk2: '/pci@1f,4000/scsi@3/disk@2,0'
disk1: '/pci@1f,4000/scsi@3/disk@1,0'
disk0:
'/pci@1f,4000/scsi@3/disk@0,0'
scsi: '/pci@1f,4000/scsi@3'
floppy: '/pci@1f,4000/ebus@1/fdthree'
ttyb:
'/pci@1f,4000/ebus@1/se:b'
ttya: '/pci@1f,4000/ebus@1/se:a'
keyboard!: '/pci@1f,4000/ebus@1/su@14,3083f8:forcemode'
keyboard:
'/pci@1f,4000/ebus@1/su@14,3083f8'
mouse:
'/pci@1f,4000/ebus@1/su@14,3062f8'
name: 'aliases'
******************************************************
So I have tried like
this and it has created a problem
********************************************************
{1} ok set NVRAM
auto-boot? false
Fast Instruction Access MMU Miss
{1} ok reset-all
Resetting
...
screen not found.
Can't open input device.
Keyboard not present. Using
ttya for input and output.
Sun Enterprise 420R (4 X UltraSPARC-II 450MHz), No
Keyboard
OpenBoot 3.29, 4096 MB memory installed, Serial #15283494.
Ethernet
address 8:0:20:e9:35:26, Host ID: 80e93526.
{0} ok probe-scsi-all
/pci@1f,4000/scsi@4,1
/pci@1f,4000/scsi@4
Target 0
Unit 0 Disk
FUJITSU MAN3367M SUN36G 1804
Target 1
Unit 0 Disk IBM
DDYST1835SUN18G S94A
Target 2
Unit 0 Disk IBM DDYST1835SUN18G S94A
Target 3
Unit 0 Disk SEAGATE ST336704LSUN36G 032C
Target e
Unit 0
Processor SYMBIOS D1000 2
/pci@1f,4000/scsi@3,1
/pci@1f,4000/scsi@3
Target 0
Unit 0 Disk SEAGATE ST318404LSUN18G 8507
Target 1
Unit 0 Disk FUJITSU MAJ3364M SUN36G 0804
Target 6
Unit 0
Removable Read Only device TOSHIBA DVD-ROM SD-M14011007
{0} ok cd
/pci@1f,4000/scsi@4
{0} ok 6 encode-int "scsi-initiator-id" property
"scsi-initiator-id" ?
{0} ok
{0} ok 6 encode-int " scsi-initiator-id" property
{0} ok device-end
{0} ok
{0} ok cd /pci@1f,4000/scsi@3
{0} ok 6 encode-int "
scsi-initiator-id" property
{0} ok device-end
{0} ok
{0} ok install-console
screen not found.
Can't open input device.
Keyboard not present. Using ttya
for input and output.
{0} ok probe-scsi-all
/pci@1f,4000/scsi@4,1
/pci@1f,4000/scsi@4
Target 0
Unit 0 Disk FUJITSU MAN3367M SUN36G 1804
Target 1
Unit 0 Disk IBM DDYST1835SUN18G S94A
Target 2---
Unit 0
Disk IBM DDYST1835SUN18G S94A
Target 3
Unit 0 Disk SEAGATE
ST336704LSUN36G 032C
Target e
Unit 0 Processor SYMBIOS D1000
2
/pci@1f,4000/scsi@3,1
/pci@1f,4000/scsi@3
Target 0
Script interrupt: No
message after disconnect
WARNING: attempt to map-out non dma-alloc'd range:
e000 ffef8000
SO what should I DO ????
Which ID should I change ??
Can I
get syntax ?? based on my existing configuration ??
So that I will be able to
see storag DISK in both the sun Servers ??
bash-2.03# prtconf
System
Configuration: Sun Microsystems sun4u
Memory size: 4096 Megabytes
System
Peripherals (Software Nodes):
SUNW,Ultra-80
packages (driver not
attached)
terminal-emulator (driver not attached)
deblocker
(driver not attached)
obp-tftp (driver not attached)
disk-label (driver not attached)
SUNW,builtin-drivers (driver not
attached)
sun-keyboard (driver not attached)
ufs-file-system
(driver not attached)
chosen (driver not attached)
openprom (driver
not attached)
client-services (driver not attached)
options,
instance #0
aliases (driver not attached)
memory (driver not attached)
virtual-memory (driver not attached)
pci, instance #0
ebus,
instance #0
auxio (driver not attached)
power,
instance #0
SUNW,pll (driver not attached)
sc (driver
not attached)
se, instance #0
su, instance #0
su, instance #1
ecpp (driver not attached)
fdthree
(driver not attached)
eeprom (driver not attached)
flashprom (driver not attached)
network, instance #0
scsi,
instance #0
disk (driver not attached)
tape (driver
not attached)
sd, instance #0
sd, instance #1
sd, instance #2 (driver not attached)
sd, instance #3 (driver not
attached)
sd, instance #4 (driver not attached)
sd,
instance #5 (driver not attached)
sd, instance #6
sd,
instance #7 (driver not attached)
sd, instance #8 (driver not
attached)
sd, instance #9 (driver not attached)
sd,
instance #10 (driver not attached)
sd, instance #11 (driver not
attached)
sd, instance #12 (driver not attached)
sd,
instance #13 (driver not attached)
sd, instance #14 (driver not
attached)
scsi, instance #1
disk (driver not attached)
tape (driver not attached)
sd, instance #15 (driver not attached)
sd, instance #16 (driver not attached)
sd, instance #17 (driver
not attached)
sd, instance #18 (driver not attached)
sd, instance #19 (driver not attached)
sd, instance #20 (driver
not attached)
sd, instance #21 (driver not attached)
sd, instance #22 (driver not attached)
sd, instance #23 (driver
not attached)
sd, instance #24 (driver not attached)
sd, instance #25 (driver not attached)
sd, instance #26 (driver
not attached)
sd, instance #27 (driver not attached)
sd, instance #28 (driver not attached)
sd, instance #29 (driver
not attached)
scsi, instance #2
disk (driver not attached)
tape (driver not attached)
sd, instance #30
sd,
instance #31
sd, instance #32
sd, instance #33
sd, instance #34 (driver not attached)
sd, instance #35 (driver
not attached)
sd, instance #36 (driver not attached)
sd, instance #37 (driver not attached)
sd, instance #38 (driver
not attached)
sd, instance #39 (driver not attached)
sd, instance #40 (driver not attached)
sd, instance #41 (driver
not attached)
sd, instance #42 (driver not attached)
sd, instance #43 (driver not attached)
sd, instance #44 (driver
not attached)
scsi, instance #3
disk (driver not attached)
tape (driver not attached)
sd, instance #45 (driver not attached)
sd, instance #46 (driver not attached)
sd, instance #47 (driver
not attached)
sd, instance #48 (driver not attached)
sd, instance #49 (driver not attached)
sd, instance #50 (driver
not attached)
sd, instance #51 (driver not attached)
sd, instance #52 (driver not attached)
sd, instance #53 (driver
not attached)
sd, instance #54 (driver not attached)
sd, instance #55 (driver not attached)
sd, instance #56 (driver
not attached)
sd, instance #57 (driver not attached)
sd, instance #58 (driver not attached)
sd, instance #59 (driver
not attached)
pci, instance #1
pci, instance #0
pci108e,1000 (driver not attached)
SUNW,qfe, instance #0
pci108e,1000 (driver not attached)
SUNW,qfe, instance #1
pci108e,1000 (driver not attached)
SUNW,qfe, instance #2
pci108e,1000 (driver not attached)
SUNW,qfe, instance #3
counter-timer (driver not attached)
SUNW,UltraSPARC-II (driver not
attached)
SUNW,UltraSPARC-II (driver not attached)
SUNW,UltraSPARC-II
(driver not attached)
SUNW,UltraSPARC-II (driver not attached)
pseudo,
instance #0
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:28:45 EDT