This discussion is locked
kyriox
Level 1 (0 points)

Q: XServer don't recognize Promise as DAS

Hi everybudy,

I have an Xserve with 10.5.8 installed. Recently we adquired a Promise VTrak E610f with four 1TB disks and a apple fibre channel pci express card. I have tried to configure the promise as 4TB DAS. I connected xserver and promise just like is indicated at the promise manual. I already have created the array following the instrutions at http://support.apple.com/kb/HT1200 and performed de LUN mapping(http://support.apple.com/kb/HT3320?viewlocale=en_US). But, the server don't recognize the new device. I supposed that I could find using the Disk utility but the device isn't listed. I checked the apple card, the initiators WWNP and all seems correct. I have seen a lot of post that we have to format the disk as local filesystem, but it don't say how. I think tha everyone are supposing that nobody has problems to recognize the device. I really appreciate any help with this or if someone could point me to a detailed manual about the topic or how to perform a debug in order to find what is wrong.

PD.
I'm not a very good english writer, but I hope you can undertand.

Thanks.

XServer, Mac OS X (10.5.8), None

Posted on Dec 8, 2010 12:16 PM

Close
kyriox

Q: XServer don't recognize Promise as DAS

  • All replies
  • Helpful answers

  • by jmyres,Helpful

    jmyres jmyres Dec 8, 2010 10:19 PM in response to kyriox
    Level 1 (80 points)
    Dec 8, 2010 10:19 PM in response to kyriox
    Based on what you've said, a quick setting to check is that the Fibre channel settings for your RAID array are configured for Arbitrated Loop and not Point-to-Point. You generally use AL when you direct attach to a server and PP when you're connecting to the fibre channel switch in a SAN.

    In the fibre channel settings for the adapter in your server either set it to PP as well, or if it's an Apple/LSI fibre card, you can just leave it on automatic.

    If that's the problem, your RAID will present as an un-formatted logical disk in Disk Utility.

    JM

  • by kyriox,

    kyriox kyriox Dec 9, 2010 10:08 AM in response to jmyres
    Level 1 (0 points)
    Dec 9, 2010 10:08 AM in response to jmyres
    Thanks for your answer.

    I have the promise directly attached I put port topology as AL and didnú work, moreover I tested with PP, but I have the same result. I will continue looking for a solution. If you have another idea it will be welcome. Thanks

  • by jmyres,Helpful

    jmyres jmyres Dec 9, 2010 10:34 AM in response to kyriox
    Level 1 (80 points)
    Dec 9, 2010 10:34 AM in response to kyriox
    Are you getting green or blue link lights on your fibre card and Promise RAID? If so, you may have a viable fibre connection, but the RAID sets you've created may not be mapped to any of your chassis ports yet.

    If so, take a look at any settings that might be described as host or LUN mapping. I haven't used your chassis, but any settings that reference an actual physical port would be what you're looking for.

    JM

  • by kyriox,

    kyriox kyriox Jan 13, 2011 11:02 AM in response to jmyres
    Level 1 (0 points)
    Jan 13, 2011 11:02 AM in response to jmyres
    Thx for your help(I have no access to the system for a month). The fibre channel lights are all in blue. Acording to the card manual it indicates a 4Gbits speed. The problem still persist and to get worse now another problem rise; each day or a couple of days I can't access to administrartion pages and I need reboot the promise device. I supposed that promise os reach lock state, because I can ping to the server and performing and nmap shows

    135/tcp open msrpc
    139/tcp open netbios-ssn
    445/tcp open microsoft-ds
    1025/tcp open NFS-or-IIS
    27000/tcp open flexlm0

    As you can see http port is not listed.

    Any suggestions are welcome.

  • by kyriox,

    kyriox kyriox Jan 13, 2011 3:49 PM in response to jmyres
    Level 1 (0 points)
    Jan 13, 2011 3:49 PM in response to jmyres
    Thx JM I had solved the problems. It was two , maybe to obvious but... First I had written an incorrect WWPN and second a deficient network cable(even though it was new).

    Job

  • by kyriox,

    kyriox kyriox Jan 13, 2011 3:52 PM in response to kyriox
    Level 1 (0 points)
    Jan 13, 2011 3:52 PM in response to kyriox
    Thx