So, we've set up OpenSM as a service in Windows, with Start Type = Automatic.
https://wchukov.blogspot.com/2019/06/fixing-this-configuration-exceeds-mtu.html
Sometimes (depending on the OS updates) the service just won't start; even if recovery options (Restart the service) are set. If we start it manually via elevated command line, it will start normally.
However, if the service is set to Automatic(Delayed Start), it will start in 240 seconds.
The problem, I believe, is in unsatisfied dependency for OpenSM in mlx4_bus,ibbus, or ipoib6x drivers that have to finish initialization before the SM is invoked.
The simplest workaround so far is to adjust the Delayed Start timer and set OpenSM service to Automatic(Delayed Start).
To do that, in Registry Editor, in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control a new DWORD key has to be created with the name AutoStartDelay. Its value can be set to 25000 decimal(value is in milliseconds, i.e 25 seconds).
Feel free to adjust the value - hopefully, you won't have to wait for 240 seconds to be online.
Tuesday, April 14, 2020
Subscribe to:
Posts (Atom)
-
IB on VMware and Windows After struggling with 6.5 and newest 6.7 ESXi, which properly work only in Ethernet mode with Connect-X cards ... -
For those who have already evolved to NetOps, manual command-by-command execution and config template copy-pasting are things of the past. ...
-
Sometimes, OpenSM service won't start automatically or restart it will fail: OpenSM 3.3.11 UMAD Entering DISCOVERING state E...