How to find the LUN Id of the newly assigned disk to Sun Solaris 5.10 Version

Suppose Storage has allocated two LUNs to the server, and we need to confirm, whether LUN is visible of not.

Server Name	CU:Ldev	Size	Chip Port	Hitachi
testnodep378/0379/0380	02:30	13.56 GB	CL5A/6A	35255
	02:2D	13.56 GB	CL5A/6A	35255

There is been a script called si_diskinfo.sh is placed at path: /sysadm/bin/SunOS

testnodep# pwd /sysadm/bin/SunOS testnodep# ls build_pca_patch_tar                lpqueues                           sc_local.sh                        si_software.sh check_nic.pl                       make_local_filelist.sh             SFT                                si_system.sh cmsu.pl                            make_vxdg.ksh                      si_accounts.sh                     si_users.sh ctmsu.sh                           memconf                            si_cleanup.sh                      si_veritas.sh date_some_time_ago                 OLD_FILES                          si_config.sh                       si_vx_dr_make.ksh driver_info.sh                     patch_setup                        si_disk_vx_dr_dgsize.ksh           solaris_services_to_disable fixup_sendmail_Sol10.ksh           patchdiag-1.0.4                    si_diskinfo.sh                     sp_daily_stats.sh fixup_sendmail_Sol9.sh             pca                                si_disksuite.sh                    SSH_default_ksh_user.profile format_lot_of_luns.Solaris.README  pca_ck_bld                         si_explorer.sh                     SSH_default_root.profile gen_horcm_from_dg.ksh              pca.20090224-01                    si_filesystems.sh                  svcadm_disable.Sol10.sh gen_pp                             prtmem.pl                          si_generic.sh                      xpinfo getLUN_Serial.sh                   rootcp_dd.sh                       si_hwinfo.sh install_patches                    rootcp_ufsdump.sh                  si_network.sh

The Output the script si_diskinfo.sh is collected at the path /sysadm/`hostname`/sysinfo in the file name called si_diskinfo.sh.out

testnodep# pwd /sysadm/testnodep/sysinfo testnodep# ls si_accounts.sh.out            si_diskinfo.sh.out            si_filesystems.sh.out         si_system.sh.out si_cleanup.sh.out             si_diskinfo.sh.out.04062011   si_hwinfo.sh.out              si_users.sh.out si_config.sh.out              si_disksuite.sh.out           si_network.sh.out             si_veritas.sh.out si_disk_vx_dr_dgsize.ksh.out  si_explorer.sh.out            si_software.sh.out            VeritasDRoutput

Before running the script si_diskinfo.sh, take the backup of the output file si_diskinfo.sh.out.

testnodep# pwd /sysadm/testnodep/sysinfo # cp –p si_diskinfo.sh.out si_diskinfo.sh.out.05062011

Now run the script si_diskinfo.sh at the path /sysadm/bin/SunOS.

testnodep# pwd /sysadm/bin/SunOS testnodep# ./si_diskinfo.sh

Now the new output file would be generated with name si_disinfo.sh.out , Now compare the file si_diskinfo.sh.out and si_diskinfo.sh.out.05062011, which will give the new disk assigned to the server.

testnodep# diff si_diskinfo.sh.out.04062011 si_disksuite.sh.out 1c1 < === testnodep  06-04-2011 00:20:15 --- > === testnodep  06-04-2011 00:20:16 3,31c3 < === /opt/SUNWexplo/bin/diskinfo.sparc <  < AVAILABLE SCSI DEVICES: < Location     Vendor          Product         Rev  Serial # <  <     c0t0d0    LSILOGIC   Logical Volume       3000 LSIInternal < c2t50060E800589B750d0 HITACHI    OPEN-V      -SUN     6007 50089B7020F < c2t50060E800589B750d1 HITACHI    OPEN-V      -SUN     6007 50089B70210 < c2t50060E800589B750d10        HITACHI    OPEN-V      -SUN     6007 50089B704FF < c2t50060E800589B750d11        HITACHI    OPEN-V      -SUN     6007 50089B70500 < c2t50060E800589B750d13        HITACHI    OPEN-V      -SUN     6007 50089B7022D < c2t50060E800589B750d14        HITACHI    OPEN-V      -SUN     6007 50089B70230 < c2t50060E800589B750d2 HITACHI    OPEN-V      -SUN     6007 50089B70211 < c2t50060E800589B750d3 HITACHI    OPEN-V      -SUN     6007 50089B70451 < c2t50060E800589B750d4 HITACHI    OPEN-V      -SUN     6007 50089B70452 < c2t50060E800589B750d5 HITACHI    OPEN-V      -SUN     6007 50089B70453 < c2t50060E800589B750d6 HITACHI    OPEN-V      -SUN     6007 50089B70454 < c2t50060E800589B750d7 HITACHI    OPEN-V      -SUN     6007 50089B704FC < c2t50060E800589B750d8 HITACHI    OPEN-V      -SUN     6007 50089B704FD < c2t50060E800589B750d9 HITACHI    OPEN-V      -SUN     6007 50089B704FE < c4t50060E8005C02410d0 HP         OPEN-V      -SUN     6007 500C0240600 < c4t50060E8005C02410d1 HP         OPEN-V      -SUN     6007 500C0240601 < c4t50060E8005C02410d2 HP         OPEN-V      -SUN     6007 500C0240602 < c4t50060E8005C02410d3 HP         OPEN-V      -SUN     6007 500C0240700 < c4t50060E8005C02410d4 HP         OPEN-V      -SUN     6007 500C0240701 < c4t50060E8005C02410d5 HP         OPEN-V      -SUN     6007 500C0240702 < c4t50060E8005C02410d6 HP         OPEN-V*2    -SUN     6007 500C0240800 < c4t50060E8005C02410d7 HP         OPEN-V      -SUN     6007 500C0240806 < c4t50060E8005C02410d8 HP         OPEN-V      -SUN     6007 500C0240804 --- > === disksuite installed, but not configured

< c2t50060E800589B750d13        HITACHI    OPEN-V      -SUN     6007 50089B7022D (LUN ID) < c2t50060E800589B750d14        HITACHI    OPEN-V      -SUN     6007 50089B70230 (LUN ID)

The above disk are the new disk attached to the server, Please find the LUN ID, which we can compare from the disk provided by the storage.