CeRedunSwitchCommand

• Base type Enumeration

The following redundancy switch command values are defined. However some platforms, group types or redundancy types may only support a subset of these commands: noCmdInEffect(1) This value should be returned by a read request when no switch command has been written to the member in question since initialization or the last command is no longer in effect due to either a later clear command or because switch commands never remain in effect on this managed system. This value may not be used in a write operation. clear(2) Clears any switch command in effect for the specified member. If the member number is sent as -1, then it clears all switch commands in effect for all members. Following a clear command, the value read back should be noCmdInEffect. manualSwitchAway(3) Switches away from the specified member, so that it will become (or remain) standby. It should succeed only if the peer member is present with no switchable alarm conditions and has no equal or higher precedence switch command in effect. forcedSwitchAway(4) Switches away from the specified member, so that it will become (or remain) standby. This should succeed when the peer member is present even when it has a degraded alarm condition or a manual switch in effect. When applied to a primary member it should not succeed if the secondary peer has a failure alarm condition. However, if applied to a secondary member it should succeed even if the peer primary member has a failure alarm condition. lockoutProtection(5) When applied to a secondary member, this command should prevent the secondary from taking over as active for any primary member. It should if necessary, cause a switch back to the corresponding primary member even when there is an existing alarm or forced switch in effect for the primary member. When applied to a primary member in a 1:n architecture, it should prevent just the one primary member from going standby.