This counts loopback replies received that this device cannot tie back to any outstanding LBM it remembers sending, distinct from the unexpected-LBR counter in that unresolved here specifically implies the device could not even determine what session or MEP the reply is meant to correlate to. In practice this is most often caused by local tracking state aging out before a delayed reply from the far end finally shows up. A cluster of unresolved LBRs shortly after a loopback session against a distant, high-latency remote MEP with an unusually long round-trip time fits this exact pattern.