Can be used to solve the multiple-manager problem. Before performing any SETs, the manager reads this value. As a VAR-BIND of the only/last SET PDU, this value is written with that value read. If some other manager had made changes, this value would have incremented, and the SET to it will fail. Note that this only guards against other managers that use this semaphore. Changes made without using this value will NOT be protected against. For this reason, it is suggested that ccCfgHistChangeCount also be SET - though that is not a perfectly fail-safe semaphore, it will in most cases protect even against this latter case.