iSNS Server ver 3 Malformed Packet - Storage
This is a discussion on iSNS Server ver 3 Malformed Packet - Storage ; Hello Group,
I have the iSNS server installed and have an array registered with it.
The array has targets for a Solaris initiator. The solaris initiator
is unable to retrieve it's targets from the server and when I look at
...
-
iSNS Server ver 3 Malformed Packet
Hello Group,
I have the iSNS server installed and have an array registered with it.
The array has targets for a Solaris initiator. The solaris initiator
is unable to retrieve it's targets from the server and when I look at
a packet trace of the attempt I see "malformed packed" in the packets
sent from the server to the client.
This is from the packet trace as viewed by wireshark...
iSNS
iSNSP Version: 1
Function ID: DevAttrQryRsp (32770)
PDU Length: 164
Flags: 0x4c00
Transaction ID: 10
Sequence ID: 0
Payload: 000000000000002100000004000000010000000000000000.. .
ErrorCode: No Error (0)
iSCSI Node Type: 0x00000001 Target
.... .... .... .... .... .... .... .0.. = Control : No
.... .... .... .... .... .... .... ..0. = Initiator : No
.... .... .... .... .... .... .... ...1 = Target : Yes
Attribute Tag: iSCSI Node Type (33)
Attribute Length: 4
Attribute Tag: Delimiter (0)
Attribute Length: 0
PG iSCSI Name: iqn.1992-08.com.netapp:sn.33603897
Attribute Tag: PG iSCSI Name (48)
Attribute Length: 36
[Malformed Packet: iSNS]
0000 00 00 0c 07 ac 34 00 16 41 53 88 6a 08 00 45 00 .....
4..AS.j..E.
0010 00 d8 41 34 40 00 80 06 a2 e5 0a 3d 11 35 0a 3c ..A4@......=.
5.<
0020 f0 58 0c 85 81 b6 88 e3 f3 79 ab e0 df 38 50 18 .X.......y...
8P.
0030 ff 87 e4 f0 00 00 00 01 80 02 00 a4 4c 00 00
0a ............L...
0040 00 00 00 00 00 00 00 00 00 21 00 00 00 04 00
00 .........!......
0050 00 01 00 00 00 00 00 00 00 00 00 00 00 30 00 00 .............
0..
0060 00 24 69 71 6e 2e 31 39 39 32 2d 30 38 2e 63 6f .$iqn.
1992-08.co
0070 6d 2e 6e 65 74 61 70 70 3a 73 6e 2e 33 33 36 30 m.netapp:sn.
3360
0080 33 38 39 37 00 00 00 00 00 31 00 00 00 40 00 00
3897.....1...@..
0090 00 00 00 00 00 00 00 00 ff ff 0a 3c f0 34 00 00 ...........<.
4..
00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 ................
00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 ................
00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 ................
00d0 00 32 00 00 00 04 00 00 0c bc 00 00 00 33 00 00 .
2...........3..
00e0 00 04 00 00 00 01 ......
Any ideas why this is happening?
Thanks,
Vic
-
RE: iSNS Server ver 3 Malformed Packet
Vic,
The DevAttrQryRsp PDU returned by Microsoft iSNS Server is well formed and
does contain an IPv4 address. It looks like the iSNS client in the initiator
queried for a PG Portal instead of a Portal. It's possible that your viewer
is not parsing the PDU correctly. Decoding it by hand gives the following PDU:
00 01 - iSNSP Version = 1
80 02 - FUNCTION ID = 0x8002 = DevAttrQryRsp
00 a4 - PDU LENGTH = 0x00a4 = 164 bytes
4c 00 - FLAGS = 0x4c00 = 01001010 00000000
00 0a - TRANSACTION ID = 0x0a = 10
00 00 - SEQUENCE ID = 0x0000 = 0
00 00 00 00 - ErrorCode = 0 = SUCCESS
**** PAYLOAD ****
00 00 00 21 - Attribute Tag = 0x21 = 33 = iSCSI Node Tpe
00 00 00 04 - Attribute Length = 4 bytes
00 00 00 01 - Attribute Value = 0x01 -> iSCSI Target
00 00 00 00 - Attribute Tag = Delimiter
00 00 00 00 - Attribute Length = 0 bytes
00 00 00 30 - Attribute Tag = 0x30 = 48 -> PG iSCSI Name
00 00 00 24 - Attribute Length = 0x24 = 36 bytes
Attribute Value =
69 71 6e 2e 31 39 39 32 2d 30 38 2e 63 6f 6d 2e 6e 65 74 61 70 70 3a 73 6e
2e 33 33 36 30 33 38 39 37 00 00 iqn.1992-08.com.netapp:sn.33603897
00 00 00 31 - Attribute Tag = 0x31 = 49 = PG Portal IP Address
00 00 00 40 - Attribute Length = 0x40 = 64 bytes
Attribute Value =
00 00 00 00 00 00 00 00 00 00 ff ff 0a 3c f0 34 00 00 -> IPv4 address
10.60.240.52
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 32 - Attribute Tag = 0x32 = 50 = PG Portal TCP Port
00 00 00 04 - Attribute Length = 4 bytes
00 00 0c bc = Attribute Value = 0xcbc = 3260
00 00 00 33 - Attribute Tag = 0x33 = 51 = PG Tag
00 00 00 04 - Attribute Length = 4 bytes
00 00 00 01 - Attribute Value = 1 -> i.e. The Portal Tag is 1
Regards,
Patrick
"Vic" wrote:
> Hello Group,
>
> I have the iSNS server installed and have an array registered with it.
> The array has targets for a Solaris initiator. The solaris initiator
> is unable to retrieve it's targets from the server and when I look at
> a packet trace of the attempt I see "malformed packed" in the packets
> sent from the server to the client.
>
> This is from the packet trace as viewed by wireshark...
>
> iSNS
> iSNSP Version: 1
> Function ID: DevAttrQryRsp (32770)
> PDU Length: 164
> Flags: 0x4c00
> Transaction ID: 10
> Sequence ID: 0
> Payload: 000000000000002100000004000000010000000000000000.. .
> ErrorCode: No Error (0)
> iSCSI Node Type: 0x00000001 Target
> .... .... .... .... .... .... .... .0.. = Control : No
> .... .... .... .... .... .... .... ..0. = Initiator : No
> .... .... .... .... .... .... .... ...1 = Target : Yes
> Attribute Tag: iSCSI Node Type (33)
> Attribute Length: 4
> Attribute Tag: Delimiter (0)
> Attribute Length: 0
> PG iSCSI Name: iqn.1992-08.com.netapp:sn.33603897
> Attribute Tag: PG iSCSI Name (48)
> Attribute Length: 36
> [Malformed Packet: iSNS]
>
> 0000 00 00 0c 07 ac 34 00 16 41 53 88 6a 08 00 45 00 .....
> 4..AS.j..E.
> 0010 00 d8 41 34 40 00 80 06 a2 e5 0a 3d 11 35 0a 3c ..A4@......=.
> 5.<
> 0020 f0 58 0c 85 81 b6 88 e3 f3 79 ab e0 df 38 50 18 .X.......y...
> 8P.
> 0030 ff 87 e4 f0 00 00 00 01 80 02 00 a4 4c 00 00
> 0a ............L...
> 0040 00 00 00 00 00 00 00 00 00 21 00 00 00 04 00
> 00 .........!......
> 0050 00 01 00 00 00 00 00 00 00 00 00 00 00 30 00 00 .............
> 0..
> 0060 00 24 69 71 6e 2e 31 39 39 32 2d 30 38 2e 63 6f .$iqn.
> 1992-08.co
> 0070 6d 2e 6e 65 74 61 70 70 3a 73 6e 2e 33 33 36 30 m.netapp:sn.
> 3360
> 0080 33 38 39 37 00 00 00 00 00 31 00 00 00 40 00 00
> 3897.....1...@..
> 0090 00 00 00 00 00 00 00 00 ff ff 0a 3c f0 34 00 00 ...........<.
> 4..
> 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 ................
> 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 ................
> 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 ................
> 00d0 00 32 00 00 00 04 00 00 0c bc 00 00 00 33 00 00 .
> 2...........3..
> 00e0 00 04 00 00 00 01 ......
>
>
> Any ideas why this is happening?
>
> Thanks,
> Vic
>
>