This accessible-for-notify object carries the ICR inconsistency error code, currently defined only as peerLoss(1), reported in an associated notification. Admins use this value inside a received trap to understand why an ICR inconsistency notification fired, specifically that the node lost contact with its redundant peer. Receiving a notification carrying peerLoss(1) would alert an admin that the ICR keepalive hold time expired and the peer chassis is presumed down.