missing port number(s) in trap 128?

missing port number(s) in trap 128?

[Jesus Camacho Villanueva]

Hello Everyone,

When OpenSM receives a trap 128 indicating a "Link state of at least
one port of switch at <LIDADDR> has changed", it seems there is not
any information about the port number(s) of the affected link(s).

Do you know if there is any chance to retrieve this information from
this trap or through other incoming MAD(s)?

Any ideas or suggestions would be greatly appreciated.

Kind regards,
Jesus Camacho
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: missing port number(s) in trap 128?

[Hal Rosenstock]

On 5/8/2014 7:51 AM, Jesus Camacho Villanueva wrote:
> Hello Everyone,
> 
> When OpenSM receives a trap 128 indicating a "Link state of at least
> one port of switch at <LIDADDR> has changed", it seems there is not
> any information about the port number(s) of the affected link(s).
> 
> Do you know if there is any chance to retrieve this information from
> this trap or through other incoming MAD(s)?
> 
> Any ideas or suggestions would be greatly appreciated.

Per current IBTA spec, port number is not included in link state change
trap 128. It would need to include a set of ports which changed state
and not just single port.

Once SM receives trap 128 from some switch, SM is responsible for
querying that switch and determining which ports changed state from
"last" time it queried them. It can do this via querying PortInfo MAD
for all the ports on that switch. PortInfo MAD contains the PortState.
SM also resets the PortStateChange bit in SwitchInfo MAD for that switch.

-- Hal

> 
> Kind regards,
> Jesus Camacho
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: missing port number(s) in trap 128?

[Jesus Camacho Villanueva]

Hal,

thanks for your quick and clear response.

Jesus


On 8 May 2014 15:20, Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> wrote:
>
> On 5/8/2014 7:51 AM, Jesus Camacho Villanueva wrote:
> > Hello Everyone,
> >
> > When OpenSM receives a trap 128 indicating a "Link state of at least
> > one port of switch at <LIDADDR> has changed", it seems there is not
> > any information about the port number(s) of the affected link(s).
> >
> > Do you know if there is any chance to retrieve this information from
> > this trap or through other incoming MAD(s)?
> >
> > Any ideas or suggestions would be greatly appreciated.
>
> Per current IBTA spec, port number is not included in link state change
> trap 128. It would need to include a set of ports which changed state
> and not just single port.
>
> Once SM receives trap 128 from some switch, SM is responsible for
> querying that switch and determining which ports changed state from
> "last" time it queried them. It can do this via querying PortInfo MAD
> for all the ports on that switch. PortInfo MAD contains the PortState.
> SM also resets the PortStateChange bit in SwitchInfo MAD for that switch.
>
> -- Hal
>
> >
> > Kind regards,
> > Jesus Camacho
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html