hello,
i am an oracle DBA and trying to scan a newly created LUN of 200 GB on fiber channel by SAN admin.we have solaris 10 and SANtoolkit is installed.i tried following to get the new LUN at my machine. go /opt/Netapp/Santoolkit/bin and then ./sanlun lun show but i see only the existing LUN? is there any issue with the creation of LUN?
kindly guide
Regards
is it mapped to the host within the storage? is the SAN configured to show it to the host (correct zoning)? what is the output of:
cfgadm -al
?
Do you see new LUN in output of format ? Do you see any messages saying something like "wrong magic number" in /var/adm/messages?
sir thanks to both of you for replying back.
LUN is mapped to the initiator and mapped correctly and the we have dataFort Decrue so LUN is encrypted there by applying cryptainer and then i have been asked to SCAN it so normally i see it as we have done this activity in last 14 data centres and things went fine but here i couldn't see it. my DB need it urgently as i am about out of space.
@bartus11 , no i cant see it in format command as well, and i will see the var/adm/messages to check your observation but if that exist so what does it mean?
Regards
Did you try the command that DukeNuke2 posted? Try it, and then run format again.
ok sir i will re-check this command and fall back.
regards
hi,
the output of cfgadm -al is attatched
@ bartus11, i have checked the / var/ adm/messages and found what you were saying and that is "wrong magic number", the output of last 100 lines is as follows.
Jan 23 11:53:20 db19 genunix: [ID 936769 kern.info] ssd100 is /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e
Jan 23 11:53:20 db19 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100):
Jan 23 11:53:20 db19 Corrupt label; wrong magic number
Jan 23 11:53:20 db19 genunix: [ID 487590 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 7320
Jan 23 11:53:20 db19 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100) multipath status: degraded, path /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w2102000e770064b5,14 is online Load balancing: round-robin
Jan 23 11:53:20 db19 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100):
Jan 23 11:53:20 db19 Corrupt label; wrong magic number
Jan 23 11:54:23 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 11:54:23 db19 last message repeated 7 times
Jan 23 11:57:35 db19 genunix: [ID 487590 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 7320
Jan 23 11:57:35 db19 last message repeated 20 times
Jan 23 11:57:35 db19 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100) multipath status: optimal, path /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fp0) to target address: w2104000e770064b5,14 is online Load balancing: round-robin
Jan 23 11:58:06 db19 CLSD: [ID 770310 daemon.notice] The clock on host db19 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
Jan 23 11:59:53 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 12:05:23 db19 last message repeated 15 times
Jan 23 12:10:47 db19 CLSD: [ID 770310 daemon.notice] The clock on host db19 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
Jan 23 12:10:53 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 12:10:53 db19 last message repeated 7 times
Jan 23 12:16:23 db19 statd[433]: [ID 766906 daemon.warning] statd: cannot talk to statd at 10.x.x.x, RPC: Authentication error(7)
Jan 23 12:16:23 db19 last message repeated 7 times
now after running the cfgadm -al i run format command but do not see it but in the /var/adm/messages i see "wrong magic number" but don't have nay idea what does it mean
kindly guide
regards
So the LUN was detected by Solaris. To confirm that the proper LUN is showing up in /var/adm/messages run: iostat -xn ssd100 , then in the disk name similar to this:
c3t600C6660000000000999A65F43D17500d0
identify four characters before "d0" part (red). It is the LUN ID. Ask your storage admin if the newly assigned LUN ID is the same as the one extracted from the disk name. If it is the case, then you have your new LUN 
edit: You can also use last four characters from your LUN path:
/scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e
which is LUN ID as well
ok sir that is correct what you said but then what does this mean:
Jan 23 11:53:20 db19 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60a98000572d51384b4a686a3333376e (ssd100):
Jan 23 11:53:20 db19 Corrupt label; wrong magic number
kindly tell me what is mean by " Corrupt label; wrong magic number" and "ssd100"
please do guide and do recommend dome reading to know all such kind of things
please
many regards
It is usual error message when new LUN is connected to the server. It indicates that there is no partition table specified there yet. Depending on what you want to do with this LUN, you might need to write new partition table (label it) with format utility.
You can read about disk management in Solaris here: http://docs.oracle.com/cd/E23823_01/html/817-5093/disksconcepts-6.html\#scrolltoc
sir i got you but kindly suggest some reading material to know all these thing related to LUN etc and one last thing if you have read the attatchement of cfgadm -al output so here we have c1 and c2 ,two 4 gig fiber cards and c1 is unconfigured . the ouput is as follows
c1 fc-fabric connected unconfigured unknown
c1::2100000e77006483 unavailable connected unconfigured failed
c1::2100001b32988752 unknown connected unconfigured unknown
c1::2104000e77006483 unavailable connected unconfigured failed
c2 fc-fabric connected configured unknown
now how i can reconfigure it
please guide
The way I see it is the following:
Have you done that? What volume manager are you using on the host (SVM, VxVM, etc.)? Are there any ports down on the SAN switch that could affect the multipathing (those "multipath status: degraded" messages aren't a good omen)? Are you using MPxIO or VxDMP as multipathing solution (looks like mpxio, but I just wanna be sure)?
Also, check those "statd - RPC" errors too (I don't know if they're related) you seem to have some remote procedure calls that can't go through because of authentication issues...
In the end, I would advise you to take into account a bug that might affect your system: Bug 6614241 - MPxIO never re-enables a previously failed iSCSI path
This is for iSCSI, but it's worth taking a look at what the output is, maybe you've misconfigured your SAN (go to support.oracle.com):
"For the Sun target we see this error frequently
Oct 5 06:25:59 sunx4200-shu02 genunix: [ID 265984 kern.warning] WARNING: Page83 data not standards compliant SUN SOLARIS 1
and for the Netapp target we see this one...
Oct 5 10:58:43 sunx4200-shu02 genunix: [ID 198094 kern.warning] WARNING: Page83 data not standards compliant NETAPP LUN 0.2
This seems to be a case of Solaris checking compliance against an old version of the spec."
Try these commands step by step and see if you can see the new LUN in the format output. Let us know...
#cfgadm -al
#devfsadm -C
#devfsadm -c disk
Momin
---------- Post updated at 01:02 PM ---------- Previous update was at 12:59 PM ----------
Dont worry about the corrupt label... that shows the new disk is seen by the OS. Run the format command and select the NEW disk/LUN. It should ask you label. Just say YES. If you you are not propmpted to label, just type label at the format prompt after selecting the new LUN to label that and that's it!
Momin