I just noticed that the host port that the SM is running on is
connected to switch port 2.
What seems to be happening is that all of the switch's ports (except
port 0) are seen as having local port number 2 in the actual PortInfo
attribute information, even though the PortNum field in the SA recor
Eitan> Could you dump out the content of the PortRecords that you
Eitan> get as response?
They look like valid records for switch ports, except the local port
number field doesn't match the port number field in the SA record
identifier wrapper.
- R.
__
: Tuesday, November 15, 2005 5:21 PM
> To: Yael Kalka
> Cc: Eitan Zahavi; openib-general@openib.org
> Subject: Re: [openib-general] SRP device management client (and a few
opensm
> glitches)
>
> Yael> Hello Roland, When turning on only the comp_mask for the
> Yael> loca
Yael> Hello Roland, When turning on only the comp_mask for the
Yael> local_port_num you will get all relevant PortInfo records
Yael> from the switches. These records do have many fields zeroed
Yael> out (e.g subnet_prefix), but they are still valid records.
Yael> Is this what y
Message-
From: Eitan Zahavi [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 11:30 AM
To: Roland Dreier; Eitan Zahavi
Cc: openib-general@openib.org
Subject: RE: [openib-general] SRP device management client (and a few
opensm glitches)
Thanks. We will try and reproduce it here.
Eitan
, 2005 10:31 AM
> To: Eitan Zahavi
> Cc: openib-general@openib.org
> Subject: Re: [openib-general] SRP device management client (and a few
opensm
> glitches)
>
> Roland> Quite easy in my setup -- it seems to happen every time on
> Roland> my fabric when I do
Roland> Quite easy in my setup -- it seems to happen every time on
Roland> my fabric when I do a get table for PortInfoRecords with
Roland> local port num 2.
And running ibsrpdm on the scinet fabric at SC'05 I see hundreds of
PortInfoRecords with a base LID of 0...
- R.
_
Eitan> Yes this is correct we never got requested for that query.
Eitan> If you are only interested in obtaining the guid of the
Eitan> port you can simply use NodeInfoRecord and you get the guid
Eitan> in the NodeInfo. But you probably know that. Is there
Eitan> anything more
Roland Dreier wrote:
The opensm issues I saw were:
- GUIDInfoRecord SA queries are not implemented (I think), so by
default my code does a (non-compliant) SM class query to get ports'
GUIDs.
Yes this is correct we never got requested for that query.
If you are only interested in obtaini
