[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    ADISC clarifications in iFCP

    • To:
    • Subject: ADISC clarifications in iFCP
    • From: Rich Ramos <>
    • Date: Fri, 29 Aug 2003 22:33:52 -0400 (EDT)
    • Date-Sent: Friday, August 29, 2003 7:31 PM -0700
    • Delivered-To:

    (note: this is now the third attempt at getting this posting to the list.  Apparently the only thing that has actually been posted to the list for a week was a virus this morning.  I think the address has been disabled due to that rash of virus postings last week, so I'm trying instead. If you respond to this please make sure to include my address in the response).
    I need a couple clarifications in regards to the ADISC ELS in iFCP.
    1. In section  Discover Address Accept (ADISC ACC), it describes the format of the ELS.
    Should everywhere that it refers to "Originator" really be "Responder", since the ACCept is really coming from the device responding to the ADISC else.   Or am I missing  some fundamental change in how iFCP does things differently than Fibre Channel?
    2. On this one I might be showing my ignorance on iFCP, so apologies if this is obvious.
    If I have a set of FC disk drives, that are on the far side of an iFCP gateway that is doing address translation, and I'm trying to figure out their 'true' ALPAs in an enclosure and not their translated ones, will ADISC be able to achieve this for me?  If I'm reading the spec correctly, it looks like the "Hard address" field will be 0 and the N_Port ID will be the translated address and therefore neither will give me the ALPA as the drive itself sees it. Is that correct?
    If so, would transparent address mode be my only solution or is there something else that would help me?


Last updated: Sat Aug 30 06:19:27 2003
12864 messages in chronological order