some problems with logical link configuration

[Ilya Kalistru]

Good day, ladies and gentleman!
Anybody alive here?
I have some problems with SubnetManager (I think).
My device (connected directly to Mellanox Infiniband line card) after physical link up and before Logical link configuration receive a lot  of strange identical packets which I don't know how to interpret.
After a few seconds after physical link up I receive another 4 Get(NodeInfo) packets and then physical link down...
Link down regardless of my GetResp(NodeInfo) (may be my packet have mistakes and subnet manager don't receive it?)

That strange packet and link down after Get(NodeInfo) may be coupled problems (and may be not..)
Could anybody help me to find error in my response packets?
May be someone knows what is in that "strange" packet?

This is example of packets data:

==============================================

This is raw data of "strange" packet without VCRC and ICRC (both checked and found valid):
F002FFFF 0048FFFF (LRH)
64400000 00000000 00000000 (BTH)
00000000 00000000 (DETH)
01810103 00000001 00000000 00000000
02C90000 000002C9 00000000 00000000
FFFFFFFF 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00040003 00002000 0000015E 00000001
00000474 00000008 00000000 (all others are 0's)

LRH means:
Virtual Lane = 15
Next header - BTH
DLID - permissive
length = x048
SLID - permissive

BTH means:
x64 = unreliable datagram "SEND only"
migrate bit is set (sic! It's strange...)
P_Key = x0000 (another strange fact)
DestQP = 0 (subnet management interface)
PSN always = 0 (strange)

DETH:
Source QP = 0

MAD header:
MgmtClass = x81 (directed route subnet)
Method = x03 (Means "SEND", but it's strange because method "send" don't defined for DirRouteSubn MgmtClass)
HopPoint = 0
HopCount = 1
AttributeID = x02C9 (I don't know what does it mean)
Attribute Modifier = x000002C9

I don't know how to interpret all other data.

====================================================

Get(NodeInfo) I've received:
F002FFFF 0048FFFF (LRH)
6400FFFF 00000000 0000001B (BTH)
00000000 00000000 (DETH)
01810101 00000101 00000001 0000407C
00110000 00000000 00000000 00000000
FFFFFFFF 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00010000  all others 0's

LRH means:
Virtual Lane = 15
Next header - BTH
DLID - permissive
length = x048
SLID - permissive

BTH means:
x64 = unreliable datagram "SEND only"
P_Key = xFFFF
DestQP = 0 (subnet management interface)
PSN = x1B
SourseQP = 0

MAD header:
MgmtClass = x81 (directed route subnet)
Method = x01 (Means "GET")
HopPoint = 1
HopCount = 1
AttributeID = x0011 (NodeInfo)
Attribute Modifier = 0
M_key = 0
DrSLID - permissive
DrDLID - permissive
InitPath - [1]

==================================================
I respond GetResp(NodeInfo)

F002FFFF 0048FFFF 6400FFFF 00000000
00000040 00000000 00000000 01810181
80000101 00000001 0002DCD4 00110000
00000000 00000000 00000000 FFFFFFFF
00000000 00000000 00000000 00000000
00000000 00000000 00000000 01010101
00000000 00000000 55554598 AF458723
55554598 AF458723 00010000 00000000
01555545 00000000 00000000 00000000
00000000 00000000 00000000 00010000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00010000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 FE92F80D
0E50

[Ilya Kalistru]

I will tell it, despite the fact that nobody here:
I've found error in my GetResponse(NodeInfo). Two VCRC were erroneously added to this packet. And now, when I've fixed this, SM requests other attributes.

But I still don't know what "strange" packet means.


среда, 18 декабря 2013 г., 22:32:25 UTC+4 пользователь Ilya Kalistru написал: