Fwd: Sun 220R and IBM ESS (shark) array

From: Nicole Skyrca (nskyrca_at_syr.edu)
Date: 10/22/04

  • Next message: egold_at_fsa.com: "DISPLAY" 
    Date: Fri, 22 Oct 2004 16:19:07 -0400
To: <sunmanagers@sunmanagers.org>

    Hello,
    I have a Sun 220R connected to an IBM ESS (shark) model 2150 with
    McData Intrepid 6040 Director switch. The HBA in the 220R is Sun part
    x6767a (Sun SorEdge 2G FC PCI Single Channel Network Adapter). When I
    do a "cfgadm -al", more times than not, it shows my disks as failing.
    But occassionally, the command will complete with no errors.

    Some history of the machine:
    When I first connected the 220R to the Shark, it was running Solaris 8
    HW 2/2002, OBP 3.23.1 7/16/99 & POST 2.0.2 10/19/98, and the firmware
    revision of the fiber channel card was 1.13.08 4/10/02. With this
    configuration, I was able to consistantly run "cfgadm -al" without any
    errors, and the disks appeared in format. (Please note that I didn't get
    to the point to install any multipathing software like mpxio or IBM's
    SDD)

    I decided to upgrade the OS and firmware to more recent levels. First,
    I upgraded the fiber channel firmware to 1.14.09 3/8/04. Next, I upgraed
    the OS to Solaris 8 HW 2/04, finally the OBP and POST to 3.31.0
    7/25/2001 and 2.30 7/31/2000 respectively. I was able to successfully
    run "cfgadm -al" after each change (although I didn't run it multiple
    times). But a few days after the changes, I'm expiriencing intermittant
    problems.

    Does anyone have any expirience with SANS and have any clues as to what
    could be the cause of the problem? I know that I changed a lot of
    stuff, so any combination of things could have broke it. I also know
    that I have a V440 running solaris 8 HW 2/04 and fiber channel cards
    with the same firmware revision, and that seems to be working ok. I'm
    new to SANS so I'm not sure what else to look at. It seems that since
    the hardware has not changed, it has to be something on my 220R.

    Here are some examples of the cfgadm output that were run within
    minutes of each other.

    bash-2.03# cfgadm -al
    Ap_Id Type Receptacle Occupant
    Condition
    c0 scsi-bus connected configured
    unknown
    c0::dsk/c0t0d0 disk connected configured
    unknown
    c0::dsk/c0t1d0 disk connected configured
    unknown
    c0::dsk/c0t6d0 CD-ROM connected configured
    unknown
    c1 scsi-bus connected unconfigured
    unknown
    c2 fc-fabric connected configured
    unknown
    c2::10000000c9333597 unknown connected unconfigured
    failed
    c2::10000000c93335e3 unknown connected unconfigured
    failed
    c2::10000000c9333709 unknown connected unconfigured
    failed
    c2::10000000c9333796 unknown connected unconfigured
    failed
    c2::10000000c93337ee unknown connected unconfigured
    failed
    c2::10000000c9333e8b unknown connected unconfigured
    failed
    c2::10000000c9333f72 unknown connected unconfigured
    failed
    c2::10000000c9333f77 unknown connected unconfigured
    failed
    c2::10000000c93f29c8 unknown connected unconfigured
    failed
    c2::210000e08b04ca21 unknown connected unconfigured
    unknown
    c2::210000e08b11beb0 unknown connected unconfigured
    unknown
    c2::5005076300c39cea disk connected configured
    failing
    c2::5005076300c49cea disk connected configured
    failing
    c2::5005076300c89cea disk connected configured
    failing
    c2::5005076300cc9cea disk connected configured
    failing
    c2::5005076300cf9cea disk connected configured
    unknown
    c2::5005076300d09cea disk connected configured
    unknown
    bash-2.03# cfgadm -al
    Ap_Id Type Receptacle Occupant
    Condition
    c0 scsi-bus connected configured
    unknown
    c0::dsk/c0t0d0 disk connected configured
    unknown
    c0::dsk/c0t1d0 disk connected configured
    unknown
    c0::dsk/c0t6d0 CD-ROM connected configured
    unknown
    c1 scsi-bus connected unconfigured
    unknown
    c2 fc-fabric connected configured
    unknown
    c2::5005076300c39cea disk connected configured
    failing
    c2::5005076300c49cea disk connected configured
    failing
    c2::5005076300c89cea disk connected configured
    failing
    c2::5005076300cc9cea disk connected configured
    failing
    c2::5005076300cf9cea disk connected configured
    failing
    c2::5005076300d09cea disk connected configured
    failing
    bash-2.03# cfgadm -al
    Ap_Id Type Receptacle Occupant
    Condition
    c0 scsi-bus connected configured
    unknown
    c0::dsk/c0t0d0 disk connected configured
    unknown
    c0::dsk/c0t1d0 disk connected configured
    unknown
    c0::dsk/c0t6d0 CD-ROM connected configured
    unknown
    c1 scsi-bus connected unconfigured
    unknown
    c2 fc-fabric connected configured
    unknown
    c2::5005076300c39cea disk connected configured
    failing
    c2::5005076300c49cea disk connected configured
    failing
    c2::5005076300c89cea disk connected configured
    failing
    c2::5005076300cc9cea disk connected configured
    failing
    c2::5005076300cf9cea disk connected configured
    failing
    c2::5005076300d09cea disk connected configured
    failing
    bash-2.03# uname -a
    SunOS libopac.syr.edu 5.8 Generic_117350-11 sun4u sparc SUNW,Ultra-60
    bash-2.03# luxadm -e port

    Found path to 1 HBA ports

    /devices/pci@1f,2000/SUNW,qlc@1/fp@0,0:devctl
    CONNECTED
    bash-2.03# cfgadm -al
    Ap_Id Type Receptacle Occupant
    Condition
    c0 scsi-bus connected configured
    unknown
    c0::dsk/c0t0d0 disk connected configured
    unknown
    c0::dsk/c0t1d0 disk connected configured
    unknown
    c0::dsk/c0t6d0 CD-ROM connected configured
    unknown
    c1 scsi-bus connected unconfigured
    unknown
    c2 fc-fabric connected configured
    unknown
    c2::10000000c93324e7 unknown connected unconfigured
    failed
    c2::10000000c9333318 unknown connected unconfigured
    failed
    c2::10000000c9333352 unknown connected unconfigured
    failed
    c2::10000000c9333549 unknown connected unconfigured
    failed
    c2::10000000c9333597 unknown connected unconfigured
    failed
    c2::10000000c93335a1 unknown connected unconfigured
    failed
    c2::10000000c93335e3 unknown connected unconfigured
    failed
    c2::10000000c93335f2 unknown connected unconfigured
    failed
    c2::10000000c93335f3 unknown connected unconfigured
    failed
    c2::10000000c9333655 unknown connected unconfigured
    failed
    c2::10000000c9333709 unknown connected unconfigured
    failed
    c2::10000000c9333796 unknown connected unconfigured
    failed
    c2::10000000c93337ee unknown connected unconfigured
    failed
    c2::10000000c9333827 unknown connected unconfigured
    failed
    c2::10000000c9333874 unknown connected unconfigured
    failed
    c2::10000000c9333e8b unknown connected unconfigured
    failed
    c2::10000000c9333ee8 unknown connected unconfigured
    failed
    c2::10000000c9333f57 unknown connected unconfigured
    failed
    c2::10000000c9333f72 unknown connected unconfigured
    failed
    c2::10000000c9333f77 unknown connected unconfigured
    failed
    c2::10000000c9333fa7 unknown connected unconfigured
    failed
    c2::10000000c93400b7 unknown connected unconfigured
    failed
    c2::10000000c93486d7 unknown connected unconfigured
    failed
    c2::10000000c93f102f unknown connected unconfigured
    failed
    c2::10000000c93f1057 unknown connected unconfigured
    failed
    c2::10000000c93f12c5 unknown connected unconfigured
    failed
    c2::10000000c93f29c8 unknown connected unconfigured
    failed
    c2::10000000c93f29ee unknown connected unconfigured
    failed
    c2::210000e08b04ca21 unknown connected unconfigured
    unknown
    c2::210000e08b05e21b unknown connected unconfigured
    unknown
    c2::210000e08b091ef6 unknown connected unconfigured
    unknown
    c2::210000e08b113993 unknown connected unconfigured
    unknown
    c2::210000e08b119795 unknown connected unconfigured
    unknown
    c2::210000e08b11beb0 unknown connected unconfigured
    unknown
    c2::210000e08b11c6b1 unknown connected unconfigured
    unknown
    c2::210000e08b1697ea unknown connected unconfigured
    unknown
    c2::5005076300c39cea disk connected configured
    unknown
    c2::5005076300c49cea disk connected configured
    unknown
    c2::5005076300c89cea disk connected configured
    unknown
    c2::5005076300cc9cea disk connected configured
    unknown
    c2::5005076300cf9cea disk connected configured
    unknown
    c2::5005076300d09cea disk connected configured
    unknown

    Thanks!
    Nicole
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: egold_at_fsa.com: "DISPLAY"

    Relevant Pages

    • Fwd: Process Restart Problem
      ... Read this before posting to Sun-Managers ... When I do a "cfgadm -al", more times than not, it shows my disks as failing. ... There are many other lists and newsgroups for which the question may be completely appropriate, and we encourage you to submit the posting there. ...
      (SunManagers)
    • Re: Extension files not loading
      ... The log file will faithfully reproduce the path I indicate in the line ... \n in Unknown on line 0" ... could be that they all are failing to find external dependencies. ...
      (comp.lang.php)
    • Summary: Sun 220R and IBM ESS (shark) array
      ... The solution turned out to be to unplug, and replug in the fiber cable. ... do a "cfgadm -al", more times than not, it shows my disks as failing. ...
      (SunManagers)
    • Re: How do I switch the language in my documents back to English?
      ... > Failing that, ... >> Unknown to as to why, all the saved documents are in a format not ...
      (microsoft.public.word.docmanagement)
    • Cant find LUNs on EVA5000 with cfgadm
      ... We have several Sun Servers connected to a HP EVA 5000 using Secure ...
      (SunManagers)