Wireshark-bugs: [Wireshark-bugs] [Bug 11078] Wireshark fails to interpret iSCSI packets with lar
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 30 Mar 2015 04:29:06 +0000

changed bug 11078


What Removed Added
CC   ntomar@vmware.com

Comment # 5 on bug 11078 from 
Hi Anish,
   Pls look @ SAM5 (http://www.t10.org/cgi-bin/ac.pl?t=f&f=sam5r20.pdf).
The LU being addressed in this trace is a Subsidiary Logical Unit (SLU) which
is part of a Logical Unit Conglomerate (Sec 4.6.10 in the above SAM5 spec)
consisting of an Administrative Logical Unit (ALU) behind which there could be
one or more SLUs. Thus the SLU is addressed using a hierarchical logical unit
number where the top level addresses the ALU and the next level addresses the
SLU within the ALU.

In this particular case the ALU is addressed using the 2 byte "Peripheral
device addressing format" (sec 4.7.7.2, table 27). So out of the total 8 byte
LUN (01 04 d2 00 00 00 00 00), the top 2 bytes (01 04) identify the ALU. This
means we have the following for the ALU address.

ADDRESS METHOD = 00b,
BUS IDENTIFIER = 01b,
LUN            = 04h

The remaining 6 bytes indentify the SLU within this ALU, using the "Six byte
extended logical unit addressing format" (Table 34). This means we have the
following for the SLU address.

ADDRESS METHOD = 00b,
LENGTH         = 10b
EXTENDED ADDRESS METHOD = 02h
LONG EXTENDED FLAT SPACE LUN = 00

See "Table 39 — Long extended flat space addressing format" for the complete
SLU format used in this trace.

Hope this is helpful!

You are receiving this mail because:
  • You are watching all bug changes.