This read-only INTEGER reports the vPC role status of the peer device, distinguishing configured role (primary or secondary) from currently operational role, including combined states like primarySecondary (configured primary, operating as secondary) or secondaryPrimary (configured secondary, operating as primary), or noneEstablished if there is no peer device. Administrators monitor this to detect role mismatches that can happen after a peer failure and recovery, since an unexpected combination can indicate the vPC domain hasn't returned to its intended role assignment. For example, seeing secondaryPrimary(3) would tell the admin the device configured as secondary is currently operating as the acting primary, likely because the true primary was down and has not yet reclaimed its role.