[ofa-general] Standby OpenSM reporting "Bad LinearFDBTop" value

[Sasha Khapyorsky]

Hi,

On 23:31 Wed 12 Mar     , Lan Tran wrote:
> 
> I was wondering if anyone has seen a similar issue or have any ideas
> on why this issue may have shown up?

I'm not familiar with this issue, but according to OpenSM code it looks
like switch bug workaround. Don't see how it should affect the normal
workflow.

> I have a Master SM and Standby SM running on two separate nodes, both
> connected to an 8-port Flextronic IB switch. Initially, both SM's came
> up fine (and negotiated mastership OK). But then the Standby SM node
> was rebooted; when the Standby SM came up again, it was outputing the
> following error in OpenSM logs:
> 
> Mar 12 17:05:57 837338 [AAAB71A0] -> OpenSM Rev:openib-3.0.13
> Mar 12 17:05:57 837371 [AAAB71A0] -> OpenSM Rev:openib-3.0.13
> Mar 12 17:05:57 838467 [AAAB71A0] -> osm_vendor_bind: Binding to port
> 0x50450134010002
> Mar 12 17:05:57 841495 [AAAB71A0] -> osm_vendor_bind: Binding to port
> 0x50450134010002
> Mar 12 17:05:57 843032 [43204940] -> osm_si_rcv_process: ERR 3610:
>                                 Bad LinearFDBTop value = 0xC000 on
> switch 0xb8cffff004879
>                                 Forcing correction to 0x0
> Mar 12 17:05:58 049623 [41401940] -> Entering STANDBY state

This shows that switch reports bad value of SwitchInfo.LinearFDBTop (you
can re-verify with 'smpquery switchinfo').

> Restarting the Standby SM doesn't help and neither does resetting the
> IB switch. In this state, no LIDS were getting assigned.

Standby SM should not do this. LIDs are assigned by master SM only. Run
'ibnetdiscover' or 'smpquery portinfo' on the local port to be sure that
node gets LIDs after reboot.

Sasha