Software Triggered Failover; User Triggered (Manual) Failover - Trango Systems TrangoLINK GigaPlus User Manual

4) The far end of the link will also failover since the transmitter switch will
cause the far end to lose lock as well. Steps 1-3 above will repeat for the
far end.
Hardware initiated failover to the backup pair will occur on the far end unit due to the
small gap in the transmitter being switched from active to standby on the local side. The
total time for the failover to occur is typically 150-200 milliseconds.
A hardware failover will only occur the following initial conditions are met, otherwise
none of the events in the Table will cause a failover.
1) A Standby unit is detected
2) The active Radio has its RX locked.
3) The election time period is over.
4) The guard time has elapsed

Software triggered failover

Software triggered failover is Initiated by the software based on the following
conditions. Software failovers will take 3- 5 seconds due to the fact that the events are
polled by the operating software inside the unit.
1) ODU PLL unlocked
2) Violation of a threshold setting when failover is configured as one of the
threshold actions.
3) Power Supply failure

User triggered (manual) failover

Initiated by user issue CLI/SNMP/web commands as shown below. Typically the only
user triggered command that should be executed is the utype_switch command, which
is used when the original active unit is restored or replaced and the operator wants to
return it to active status. The other commands are listed to make the operator aware
that they will cause an unintentional (and usually undesired) failover.
Commands that will force a failover
1. Using the utype_switch command to restore the active after a failover
a. This command can only be initiated on the Active unit.
b. A low level command is sent from Active to Standby unit to turn
Trango Systems, Inc.
on transmitter.
GigaPlus User Manual Rev 3.1
44