This trap-only object carries the local device's HRP priority value at the time of an HRP state-change event. Admins use it, together with hwHrpTrapPeerPriority, to understand why a particular device became active or standby, since HRP typically uses priority to arbitrate which unit takes the active role. A lower local priority value than the peer's, seen in this trap, would explain why this device yielded the active role to its peer.