Feeds:
Posts
Comments

Archive for the ‘Hardware’ Category

# cat /proc/driver/cciss/cciss0
cciss0: HP Smart Array 5i Controller
Board ID: 0x40800e11
Firmware Version: 2.66
IRQ: 10
Logical drives: 3
Current Q depth: 0
Current # commands on controller: 0
Max Q depth since init: 128
Max # commands on controller since init: 128
Max SG entries since init: 31

Sequential access devices: 0

cciss/c0d0:       69.45GB       RAID 1(0+1)
cciss/c0d1:       69.45GB       RAID 1(0+1)
cciss/c0d2:       69.45GB       RAID 1(0+1)

 

Download

HP Array Configuration Utility for Linux

Hp Array Configuration Utility CLI for Linux

HP Array Diagnostics Utility for Linux

HP System management HomePage for Linux (x86)

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3291842&prodTypeId=15351&prodSeriesId=396616&swLang=8&taskId=135&swEnvOID=1097#7832

 

Install the System management Homepage

# rpm -ivh hpsmh-< version >.linux.i386.rpm

To run HPSMH

#/etc/init.d/hpsmhd start

 

Install HP Array Configuration Utility for Linux

# rpm -ivh cpqacuxe-8.25-5.noarch.rpm

The software resides in /usr/lib, /opt/compaq/cpqacuxe and the executable name is cpqacuxe which is located in /usr/sbin.

The password resetting utility is hphmmopasswd that is located in /opt/compaq/cpqacuxe/bld.

 

Running the Array Configuration Utility

Use “cpqacuxe” for the local access only or

“cpqacuxe -R” for remote access

 

Type "http://SERVERNAME:2301" into the url field. The servername should 
be the IP address or server name of the host on which the ACU server
is running.
Use root Username and Password for login

Supported Controllers

  Smart Array 5312 Controller
  Smart Array 5302 Controller
  Smart Array 5304 Controller
  Smart Array 532 Controller
  Smart Array 5i Controller
  Integrated Smart Array Controller
  Smart Array 4200 Controller
  Smart Array 4250ES Controller
  Smart Array 431 Controller
  Smart Array 3200 Controller
  MSA500 Controller
  MSA1000 Controller
  Smart Array 641 Controller
  Smart Array 642 Controller
  Smart Array 6400 Controller
  Smart Array 6400 EM Controller
  Smart Array 6i Controller
  MSA500 G2 Controller
  MSA1500 CS Controller
  MSA20 Controller
  Smart Array P600 Controller
  Smart Array P400 Controller
  Smart Array P400i Controller
  Smart Array E200 Controller
  Smart Array E200i Controller
  Smart Array P800 Controller
  Smart Array E500 Controller

Advertisements

Read Full Post »

Solaris 10 comes with Leadville stack, is basically the code name for the StorEdge SAN Foundation Software (SFS) which Sun developed for the Solaris OS. Leadville is a new, open standards-based I/O framework and device driver stack to support FC which includes I/0 stack, Sun StorageTek Traffic Manager software (multipathing or MPxIO), Storage Networking Industry Association (SNIA) libraries, and utilities.

Advantages:

  • Ability to dynamically add new devices without rebooting
  • Automatic persistent binding
  • Virtually limitless scalability
  • Integrated multi-pathing
  • No third-party patches

Solaris 10 comes with installed Driver and utility support for Sun branded Qlogic and Emulex HBAs.

SUNWemlxs              Emulex-Sun LightPulse Fibre Channel Adapter (FCA) driver

SUNWemlxu              Emulex-Sun LightPulse Fibre Channel Adapter Utilties

SUNWqlc                         Qlogic ISP 2200/2202 Fibre Channel Device Driver
SUNWqlcu                       Qlogic Fibre Channel Adapter Utilities

bash-3.00# pkginfo -l SUNWemlxs
   PKGINST:  SUNWemlxs
      NAME:  Emulex-Sun LightPulse Fibre Channel Adapter (FCA) driver (root)
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  11.10.0,REV=2005.01.30.01.58
   BASEDIR:  /
    VENDOR:  Emulex Corporation
      DESC:  Device driver for Emulex-Sun LightPulse Fibre Channel adapters
    PSTAMP:  bogglidite20051214103253
  INSTDATE:  Dec 20 2006 11:03
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:        5 installed pathnames
                   3 shared pathnames
                   3 directories
                   1 executables
                5586 blocks used (approx)

bash-3.00# pkgchk -v SUNWemlxs
/kernel
/kernel/drv
/kernel/drv/emlxs.conf
/kernel/drv/sparcv9
/kernel/drv/sparcv9/emlxs

bash-3.00# pkginfo -l SUNWemlxu
   PKGINST:  SUNWemlxu
      NAME:  Emulex-Sun LightPulse Fibre Channel Adapter Utilties (usr)
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  11.10.0,REV=2005.01.30.01.58
   BASEDIR:  /
    VENDOR:  Emulex Corporation
      DESC:  Support software for Emulex-Sun LightPulse Fibre Channel adapters
    PSTAMP:  bogglidite20060308101102
  INSTDATE:  Dec 20 2006 11:03
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:        6 installed pathnames
                   5 shared pathnames
                   5 directories
                   1 executables
                1331 blocks used (approx)

bash-3.00# pkgchk -v SUNWemlxu
/usr
/usr/lib
/usr/lib/mdb
/usr/lib/mdb/kvm
/usr/lib/mdb/kvm/sparcv9
/usr/lib/mdb/kvm/sparcv9/emlxs.so

bash-3.00# pkginfo -l SUNWqlc
   PKGINST:  SUNWqlc
      NAME:  Qlogic ISP 2200/2202 Fibre Channel Device Driver
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  11.10.0,REV=2005.01.04.14.31
   BASEDIR:  /
    VENDOR:  Sun Microsystems, Inc.
      DESC:  Qlogic ISP 2200/2202 Fibre Channel Device Driver
    PSTAMP:  bogglidite20050914173826
  INSTDATE:  Mar 05 2008 16:32
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:        5 installed pathnames
                   3 shared pathnames
                   3 directories
                   1 executables
                2340 blocks used (approx)

bash-3.00# pkgchk -v SUNWqlc
/kernel
/kernel/drv
/kernel/drv/qlc.conf
/kernel/drv/sparcv9
/kernel/drv/sparcv9/qlc

bash-3.00# pkginfo -l SUNWqlcu
   PKGINST:  SUNWqlcu
      NAME:  Qlogic Fibre Channel Adapter Utilities (usr)
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  11.10.0,REV=2006.02.21.03.25
   BASEDIR:  /
    VENDOR:  Sun Microsystems, Inc.
      DESC:  Utilties associated with the Qlogic Fibre Channel Adapter
    PSTAMP:  bogglidite20060222001745
  INSTDATE:  Mar 05 2008 16:32
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
     FILES:        6 installed pathnames
                   5 shared pathnames
                   5 directories
                   1 executables
                  48 blocks used (approx)

bash-3.00# pkgchk -v SUNWqlcu
/usr
/usr/lib
/usr/lib/mdb
/usr/lib/mdb/kvm
/usr/lib/mdb/kvm/sparcv9
/usr/lib/mdb/kvm/sparcv9/qlc.so

Check for the current support table for Sun-branded Qlogic and QLogic-branded Qlogic fibre-channel HBAs

http://blogs.sun.com/jmcp/entry/current_sun_qlogic_fc_hba

Check for the current support table for Sun-branded Emulex and Emulex-branded Emulex fibre-channel HBAs

http://blogs.sun.com/jmcp/entry/current_sun_emulex_fc_hba

If you are using Emulex HBA in Solaris 10, Emulex driver for Solaris Sun StorageTek SAN Foundation Software (SFS) Fibre Channel adapter (FCA) on the top of Leadville for extra functionality.

http://www.emulex.com/support/solaris/index.jsp

 

Frequently asked questions

http://otmanix.de/wp-content/uploads/2007/08/emc-faq-sun-solaris-native-hbas-and-drivers.pdf

Read Full Post »

This is some information/walkthrough of getting Solaris 10 hooked up to a SAN. Also info on SUN/STK NAS devices. I think the SUN/STK NAS’s are way nicer then NetApps. Also covers SUN 6000 series array setup. A few Brocade notes also. Covers UFS and Veritas vxvm and vxfs setup for new LUNs. This is a walkthrough/notes I created while setting up some equipment, enjoy. I am seeing a good deal of visits to this page, and I am glad it is of service.

http://3rdstone.net/docs/SAN_Setup.htm

 

Nice article

Read Full Post »

The most commonly used command to determine very specific information about these two storage devices.

# luxadm probe
# luxadm display controller_number
# luxadm display enclosure_name
# luxadm display logical_path
# luxadm display enclosure_name, disk_location
# luxadm fcode_download -p

Like:

  • WWN (12 or 16 digits)
  • Enclosure Name
  • Number Disks Installed
  • Number of Controller

The luxadm utility does not recognize the Sun StorEdge D1000 array.Specific array information must be gathered using other tools such as the
format utility and visual identification.

Read Full Post »

Details:
This specific procedure must be used when replacing one of the internal fibre drives within the following servers and/or arrays:

  Sun Fire 280R, V480, and V880.
  SENA A5X00 Arrays.

Note: Failure to follow this procedure could result in a duplicate device entry for the replaced disk in Volume Manager. This is most notable when running a vxdisk list command.

Example:

 # vxdisk list
 DEVICE       TYPE      DISK         GROUP      STATUS
 c1t0d0s2     sliced       rootdisk      rootdg        online
 c1t1d0s2     sliced        -               -                error
 c1t1d0s2     sliced        -               -                error

1. Select vxdiskadm option 4 – Select the Volume Manager disk to be replaced

2. luxadm -e offline <device_path> – detach ssd instance

Use luxadm to get this disk out of the Solaris kernel configuration. The device path should end in “,raw” (for example, pci@1f,0/ide@d/dad@0,0:a,raw). This is the path from the /devices directory, not /dev/rdsk/c?t?d?s?.

  • If the disk is multipathed, run the luxadm -e offline on the second path as well

3. devfsadm -C

 The -C option cleans up the /dev directory, and removes any lingering logical links to the device link names. 
 It should remove all the device paths for this particular disk. This can be verified with:

      # ls -ld /dev/dsk/c1t1d* - This should return no devices entries for c1t1d*.

4. The drive can now be pulled physically

5. luxadm insert_device

This is an interactive command. It will go through the steps to insert the new device and create the necessary entries in the Solaris device tree.

6. vxdctl enable

This is for Volume Manager to rescan the disks. It should pick up the new disk with an “error” status. If not in error, the disk might contain some Volume Manager information, and might need to be formatted.

7. Select vxdiskadm option 5

This will start the recovery process (if needed).

Example show is for c1t0d0s2, please use your c#t#d#s# in place of for your problem.

 # vxdisk list

 c1t0d0s2 sliced - - error
 c1t0d0s2 sliced - - error
 c1t1d0s2 sliced disk01 rootdg online
 - - root-disk rootdg removed was:c1t0d0s2

Remove c1t0d0s2 entries from vxvm control.
Do “vxdisk -f rm c1t0d0s2” for all the duplicate entries.
[since there is no telling which one is the valid one, do
it for all …there can be more than 2 duplicate entries
also …]

 # vxdisk rm c1t0d0s2

 # vxdisk rm c1t0d0s2 <-- do it again to remove all the entries.

2. Remove the disk c1t0d0s2 using luxadm.

  Remove device c1t0d0s2 using "luxadm remove_device" command.

  [luxadm remove_device cxtxdxsx]

   1.luxadm remove_device /dev/rdsk/c1t0d0s2

   Pull the disk out as per luxadm instructions.

3. Run command “devfsadm -C”

4. Run command “vxdctl enable”

[Till this point, we have removed the dev_t corresponding to the physical disk. Now we will remove all the stale dev_t’s.] Please loop as per below instructions.

LOOP :

 [notice that there is one entry less, since we can have more than 2 duplicate

entries]

   # vxdisk list
   c1t0d0s2 sliced c1t0d0 - error
   c1t1d0s2 sliced disk01 rootdg online
   - - root-disk rootdg removed was:c1t0d0s2

5. Again remove *ALL* duplicate c1t0d0s2 entries from vxvm control.

   # vxdisk rm c1t0d0s2

6. Run command “luxadm -e offline <device path>” on *ALL THE PATHS* to the disk [this removes the stale dev_t. The test machine has 2 paths to the disk, one through controller c1, and the other through controller c2.

   # luxadm -e offline /dev/dsk/c1t0d0s2

   # luxadm -e offline /dev/dsk/c2t0d0s2

7. Run command “devfsadm -C”

8. Run command “vxdctl enable”

goto LOOP:
[Continue this process until there are no more entries in vxdisk list of corresponding disk c1t0d0s2 ]

Result:

   # vxdisk list
   DEVICE TYPE DISK GROUP STATUS
   c1t0d0s2 sliced root-disk rootdg online
   c1t1d0s2 sliced disk01 rootdg online

Now both OS device tree and VxVM are in a clean state corresponding to disk c1t0d0s2.

Read Full Post »

Install the Sun StorageTek PCI Express Enterprise 4 Gb FC HBA Emulex in your system:

 

image 

image

 

To Apply Power

1. Verify that the HBA is securely installed in the computer.
2. Verify that the correct optical cable is attached.
3. Plug in and power on the computer.
4. Observe light-emitting diodes (LEDs) for POST results.
Yellow, green, and amber LEDs can be seen through openings in the HBA’s
mounting bracket. Each port has a corresponding set of yellow, green, and amber
LEDs.

 

To Verify Proper Installation in SPARC Platforms

1. Enter the show-devs command at the ok prompt to list the installed devices.
The HBA can be identified in the output containing the SUNW,emlxs@n and
SUNW,emlxs@n,1 node names, where n is usually a single-digit number from 0 to 9.
2. To positively identify the port as a Sun StorageTek 4 Gb FC port, cd to the
SUNW,emlxs@N entries and enter .properties as shown in the example that
follows.

In the following example, there are two Dual Channel SG-XPCIE2FC-EM4 and one
single-channel SG-XPCIE1FC-EM4 adapters installed:

{0} ok show-devs
/pci@7c0
/pci@780
/cpu@1b
/cpu@1a
/cpu@19
/cpu@18
/cpu@17
/cpu@16
/cpu@15
/cpu@14
/cpu@f
/cpu@e
/cpu@d
/cpu@c
/cpu@b
/cpu@a
/cpu@9
/cpu@8
/cpu@7
/cpu@6
/cpu@5
/cpu@4
/cpu@3
/cpu@2
/cpu@1
/cpu@0
/virtual-devices@100
/virtual-memory
/memory@m0,800000
/aliases
/options
/openprom
/chosen
/packages
/pci@7c0/pci@0
/pci@7c0/pci@0/pci@9
/pci@7c0/pci@0/pci@8
/pci@7c0/pci@0/pci@2
/pci@7c0/pci@0/pci@1

/pci@7c0/pci@0/pci@9/SUNW,emlxs@0
/pci@7c0/pci@0/pci@9/SUNW,emlxs@0/fp@0,0
/pci@7c0/pci@0/pci@9/SUNW,emlxs@0/fp@0,0/disk
/pci@7c0/pci@0/pci@8/SUNW,emlxs@0,1
/pci@7c0/pci@0/pci@8/SUNW,emlxs@0
/pci@7c0/pci@0/pci@8/SUNW,emlxs@0,1/fp@0,0
/pci@7c0/pci@0/pci@8/SUNW,emlxs@0,1/fp@0,0/disk
/pci@7c0/pci@0/pci@8/SUNW,emlxs@0/fp@0,0
/pci@7c0/pci@0/pci@8/SUNW,emlxs@0/fp@0,0/disk
/pci@7c0/pci@0/pci@2/network@0,1
/pci@7c0/pci@0/pci@2/network@0
/pci@7c0/pci@0/pci@1/pci@0,2
/pci@7c0/pci@0/pci@1/pci@0
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/tape
/pci@7c0/pci@0/pci@1/pci@0/ide@8
/pci@7c0/pci@0/pci@1/pci@0/usb@6
/pci@7c0/pci@0/pci@1/pci@0/usb@5
/pci@7c0/pci@0/pci@1/pci@0/isa@2
/pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom
/pci@7c0/pci@0/pci@1/pci@0/ide@8/disk
/pci@7c0/pci@0/pci@1/pci@0/usb@6/hub@1
/pci@7c0/pci@0/pci@1/pci@0/isa@2/serial@0,3f8
/pci@780/pci@0
/pci@780/pci@0/pci@9
/pci@780/pci@0/pci@8
/pci@780/pci@0/pci@2
/pci@780/pci@0/pci@1
/pci@780/pci@0/pci@8/SUNW,emlxs@0,1
/pci@780/pci@0/pci@8/SUNW,emlxs@0
/pci@780/pci@0/pci@8/SUNW,emlxs@0,1/fp@0,0
/pci@780/pci@0/pci@8/SUNW,emlxs@0,1/fp@0,0/disk
/pci@780/pci@0/pci@8/SUNW,emlxs@0/fp@0,0
/pci@780/pci@0/pci@8/SUNW,emlxs@0/fp@0,0/disk
/pci@780/pci@0/pci@1/network@0,1
/pci@780/pci@0/pci@1/network@0

/virtual-devices@100/led@d
/virtual-devices@100/explorer@c
/virtual-devices@100/sunmc@b
/virtual-devices@100/sunvts@a
/virtual-devices@100/fma@9
/virtual-devices@100/echo@8
/virtual-devices@100/loop@7
/virtual-devices@100/loop@6
/virtual-devices@100/ncp@4
/virtual-devices@100/rtc@3
/virtual-devices@100/nvram@3
/virtual-devices@100/console@1
/openprom/client-services
/packages/SUNW,asr
/packages/obp-tftp
/packages/kbd-translator
/packages/dropins
/packages/terminal-emulator
/packages/disk-label
/packages/deblocker
/packages/

The following .properties output shows the properties of the two ports in one of
the dual port adapters.

{0} ok cd /pci@7c0/pci@0/pci@8/SUNW,emlxs@0
{0} ok .properties
assigned-addresses 82080010 00000000 03500000 00000000
00002000
82080018 00000000 03502000 00000000 00002000
81080020 00000000 00003000 00000000 00000100
82080030 00000000 03540000 00000000 00040000
port_wwn 10 00 00 00 c9 4b 3b 38
node_wwn 20 00 00 00 c9 4b 3b 38
alternate-reg 01080020 00000000 00000000 00000000
00000100
reg 00080000 00000000 00000000 00000000 00000000
03080010 00000000 00000000 00000000 00001000
03080018 00000000 00000000 00000000 00000100
02080030 00000000 00000000 00000000 00020000
compatible pci10df,fc20
clock-frequency 02625a00
#size-cells 00000000
#address-cells 00000002
copyright Copyright (c) 2005 Emulex
model LPe11002-S
name SUNW,emlxs
device_type scsi-fcp
manufacturer Emulex
fcode-version 1.50a8
fcode-rom-offset 0000c000
devsel-speed 00000000
class-code 000c0400
interrupts 00000001
latency-timer 00000000
cache-line-size 00000010
max-latency 00000000
min-grant 00000000
subsystem-id 0000fc22
subsystem-vendor-id 000010df
revision-id 00000002
device-id 0000fc20
vendor-id 000010df
{0} ok cd /pci@7c0/pci@0/pci@8/SUNW,emlxs@0,1
{0} ok .properties

assigned-addresses 82080110 00000000 03504000 00000000
00002000
82080118 00000000 03506000 00000000 00002000
81080120 00000000 00003100 00000000 00000100
82080130 00000000 03580000 00000000 00040000
port_wwn 10 00 00 00 c9 4b 3b 39
node_wwn 20 00 00 00 c9 4b 3b 39
alternate-reg 01080120 00000000 00000000 00000000
00000100
reg 00080100 00000000 00000000 00000000 00000000
03080110 00000000 00000000 00000000 00001000
03080118 00000000 00000000 00000000 00000100
02080130 00000000 00000000 00000000 00020000
compatible pci10df,fc20
clock-frequency 02625a00
#size-cells 00000000
#address-cells 00000002
copyright Copyright (c) 2005 Emulex
model LPe11002-S
name SUNW,emlxs
device_type scsi-fcp
manufacturer Emulex
fcode-version 1.50a8
fcode-rom-offset 0000c000
devsel-speed 00000000
class-code 000c0400
interrupts 00000002
latency-timer 00000000
cache-line-size 00000010
max-latency 00000000
min-grant 00000000
subsystem-id 0000fc22
subsystem-vendor-id 000010df
revision-id 00000002
device-id 0000fc20
vendor-id 000010df
{0} ok

To Verify Attached Storage to the Installed HBA
If online storage is connected to the HBA, use the apply show-children command
to list the attached storage.
In the example that follows, a storage JBOD has twelve targets attached to one port
of the dual-ported HBA.

{0} ok apply show-children /pci@7c0/pci@0/pci@9/SUNW,emlxs@0
Device ALPA b6 WWPN 215000c0ff00223d
LUN 0 ESI Device SUN StorEdge 3510F D1046
Link attention
Device ALPA b9 WWPN 2100000c50c30555
LUN 0 Disk SEAGATE ST3146807FC 0006
Device ALPA ba WWPN 2100000c50c30525
LUN 0 Disk SEAGATE ST3146807FC 0006
Device ALPA bc WWPN 500000e010172831
LUN 0 Disk FUJITSU MAP3147F SUN146G0301
Device ALPA c3 WWPN 2100000c50c3051b
LUN 0 Disk SEAGATE ST3146807FC 0006
Device ALPA c5 WWPN 2100000c50c30567
LUN 0 Disk SEAGATE ST3146807FC 0006
Device ALPA c6 WWPN 500000e0101727d1
LUN 0 Disk FUJITSU MAP3147F SUN146G0301
Device ALPA c7 WWPN 21000004cf64f1db
LUN 0 Disk SEAGATE ST336752FSUN36G 0508
Device ALPA c9 WWPN 2100000c50c30513
LUN 0 Disk SEAGATE ST3146807FC 0006
Device ALPA ca WWPN 500000e0101727b1
LUN 0 Disk FUJITSU MAP3147F SUN146G0301
Device ALPA cb WWPN 2100000c50c3050e
LUN 0 Disk SEAGATE ST3146807FC 0006
Device ALPA cc WWPN 21000004cf64dc04
LUN 0 Disk SEAGATE ST336752FSUN36G 0508
Device ALPA cd WWPN 21000004cf5728c0
LUN 0 Disk SEAGATE ST373307FSUN72G 0407
{0} ok

Note – You may need to use the reset-all command before entering apply
show-children.

Installing the HBA Driver with the Solaris 10 OS

After you have completed the hardware installation and powered on the computer,
follow these instructions to install the HBA driver with the Solaris 10 Operating
System (OS) (SPARC Platform Edition).
You must first install the appropriate Sun Solaris 10 OS for your platform, then
install the latest available Solaris 10 cluster patches.
Packages
Note – The following packages are required only for Solaris 10 03/05 and Solaris 10
HW1 releases. Any Solaris releases beyond these do not require the installation of
these packages.
Perform the following steps to download the Solaris 10 packages.
1. Go to the URL:
http://www.sun.com/download/products.xml?id=42c4317d
The Products Download page is displayed.
2. Under Platform, click Download.
The Login menu is displayed.
3. Type your Username and Password and click Login.
The Download page is displayed with two items available in the table.

Description File Name
Solaris 10 Sun StorEdge Enterprise 4Gb FC
Single and Dual Port HBA, English
s10_emlxs_pkgs.tar.Z
Sun StorEdge Enterprise 4Gb FC Single and
Dual Port Host Adapter README file, English

4. Read the license agreement and accept or decline.
5. Click the download item that is appropriate for this 4 Gbit adapter
The following packages are contained in the zipped file:

  • SUNWemlxs  ■ SUNWemlxu

6. Click the second item and print these driver README installation instructions.
7. Follow the README instructions.
Patches
Note – The installation of the following patch is required only for Solaris 10 releases
up through Solaris Update 1 and Solaris 10 HW2.

Perform the following steps to download the Solaris 10 patches.
1. Go to http://sunsolve.sun.com.
The SunSolve Online license agreement page is displayed.
2. Accept the License Agreement.
The SunSolve Online page is displayed.
3. Under Patches and Updates, click PatchFinder.
4. Download the following patch by typing the patch ID (without the dash number)
in the Enter Patch ID box and click Find Patch.
■ 120222-06 (or above) SunOS 5.10: Emulex-Sun Fibre LightPulse Channel Adapter
driver
5. Follow the instructions to install each patch.
6. Reboot your system after installing the patches.

Read Full Post »

Description:
This document describes the process of replacing a failed internal
disk on the Sun Fire[TM] V440 server when the disk is not mirrored using the
on-board hardware RAID controller.

Document Body:
1. Verify which disk drive corresponds with which logical device name and
physical device name. Listed below is the table for the v440 disk devices:

Disk Slot Number Logical Device Name[1] Physical Device Name
—————————————————————————–
Slot 0 c1t0d0 /devices/pci@1f,700000/scsi@2/sd@0,0

Slot 1 c1t1d0 /devices/pci@1f,700000/scsi@2/sd@1,0

Slot 2 c1t2d0 /devices/pci@1f,700000/scsi@2/sd@2,0

Slot 3 c1t3d0 /devices/pci@1f,700000/scsi@2/sd@3,0

2. Verify that a hardware disk mirror does not exist

#raidctl
No RAID volumes found.

****NOTE**** If Raid volumes exist see infodoc 73040

3. View status of SCSI devices
#cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
c2 scsi-bus connected configured unknown
c2::dsk/c2t2d0 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb1/1 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok

4. Remove the disk drive from the device tree

#cfgadm -c unconfigure <Ap_Id>
example -> #cfgadm -c unconfigure c1::dsk/c1t3d0
This example removes c1t3d0 from the device tree. The blue OK-to-Remve LED for
the disk being removed will become lit.

5. Verify that the device has been removed from the device tree

#cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 unavailable connected unconfigured unknown
c2 scsi-bus connected configured unknown
c2::dsk/c2t2d0 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb1/1 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok

*NOTE that c1t3d0 is now unavailable and unconfigured. The disks blue
OK-to-Remve LED is lit

6. Remove the disk drive

7. Install a new disk drive

8. Configure the new disk drive

#cfgadm -c <Ap_Id>
example->#cfgadm -c configure c1::dsk/c1t3d0

*NOTE that the green activity LED flashes as the new disk at c1t3d0 is added to
the device tree

9. Verify that the new disk drive is in the device tree

#cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
c2 scsi-bus connected configured unknown
c2::dsk/c2t2d0 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb1/1 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok

Read Full Post »

Older Posts »