SSV Instruction Operation

Modifications made by SSV instructions are local to the primary controller and are not crossloaded to the secondary while the system is qualifying, locking, or locked. This behavior can create configuration mismatches in redundancy systems if changes are not manually replicated, which can impact high availability. To maintain redundancy integrity, avoid making critical SSV changes during redundancy transitions and make sure that any updates are documented and applied consistently across both controllers. For systems requiring uninterrupted operation, plan SSV usage carefully and only perform changes when redundancy is stable and controllers are fully synchronized.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal