Symptom
OOB Queue Stall and SIF available credits becoming zero
Stack split happens and merge doesn't occur.
Conditions
The issue can happen when there is relatively high OOB traffic which could result in exhaustion of handle space/metadata for buffers used in OOB transactions.
This further results in stall of the OOB TX queue preventing any control packet exchange between the stack members.
Workaround
Reload of the stack member whose OOB TX queue is stalled.
Further Problem Description
When stack splits and tries to merge back, there could be relatively high control packet exchange which can lead to OOB queues of one of the switches getting stalled.
Once stalled, the switch will become unresponsive to any SDP requests from peers and this switch would get isolated from rest of the stack.