Mocomtech CRS-300 - Manual (Page 168)

CRS-300 1:10 Redundancy Switch Revision 16
Modem, RMI/TMI, and Switch Configuration MN/CRS300.IOM
5–24
5.5.3.4.2 Set Restore Holdoff Period
The "Restore Holdoff" setting, which is also programmable from 1 to 99 seconds, determines the
Switch's ability to automatically put a backed-up Traffic Modem online again if its fault clears.
Normally, a failed modem that was taken offline will remain offline indefinitely. If the fault
clears, traffic will be returned to the unit (in Auto mode) only if another Traffic Modem then
fails.
If the fault on the originally failed modem has been clear for the full programmed Restore
Holdoff time, the Switch places that modem back online, and bridges the newly faulted modem.
If the new fault is sustained, the Redundant Modem can then be used to backup the newly faulted
modem.
If the Priority selection (see Chapter 7.4.3 CONFIG Æ OPTIONSÆ PRIORITY ) is not enabled,
the Switch deals with Traffic Modem failures on a "first come, first serve" basis. If the User sets
the Switch to bridge the highest priority circuit, switching time will be minimized in the event of
a failure. If two faults occur simultaneously and are both sustained for the holdoff time, the
lower-numbered circuit will be backed up.
To set the Restore Holdoff Period :
Step Procedure
1 Go to the CONFIG Æ OPTIONS Æ HOLDOFFS menu.
2 Change the RESTORE HOLDOFF to any number in the range of 1 to 99 seconds.
5.5.3.5 Set Alarm Masking
Another way to adjust the Switch's reaction in Auto mode is to mask modem faults. The User
may disable modem Rx, Tx or both fault types so that the Switch does not react to them. This
masking prevents the Switch from taking automatic action and prevents the logging of the faults
in the stored events list.
These masks are global to all the modems attached to the Switch.
To set Alarm Masks :
Step Procedure
1 Go to CONFIG Æ OPTIONS Æ MASKS Æ MODEM-ALARMS.
2 Set the mask parameters as desired.
In the event that a second fault occurs, another way to influence Switch behavior is via Priority
Mode. For detailed information on Priority Mode, refer to
Chapter 7.4.3 CONFIG Æ
OPTIONS Æ PRIORITY.