Active OVSDB connection to wrong IP or port causes southbound operational MD-SAL to stop working

Attempting to make an active OVSDB connection via the config MD-SAL to a wrong port number (resulting in 'connection refused'), or to the wrong IP address (resulting in 'no route to host') results in the soutbound provider to stop working. That is, no more updates are made to the operational MD-SAL.