User's Manual
MC-Series Outdoor Pole Mount Users Guide998-5005-01 Rev X1
MC-Series ©2007 RadioFrame Networks, Inc. 5-13
CONFIDENTIAL AND PROPRIETARY
5.6 RadioBlade Troubleshooting
In addition to the above-mentioned errors, if the system loses communication with a
RadioBlade transceiver or is unable to read the EEPROM from the blade, then that
blade is put into an error state and if a standby blade is available it will switch over
automatically.
5.6.1 RadioBlade Locking Policy
The RadioBlade locking policy defines the actions taken by the system when a
determination is made that a RadioBlade transceiver should no longer be allowed
to remain active. This could be the result of an alarm, insertion, removal or
intervention (the user specifically locking the RadioBlade transceiver).
In general, the policy is that if a blade is taken out of service and a standby
RadioBlade transceiver is available, then the standby RadioBlade transceiver will
go into service. If no standby RadioBlade transceiver is available then the
associated BR(s) will be locked. (For the Multi-Channel RadioBlade transceiver,
the locking event locks all carriers.)
The RadioBlade locking policy is enabled by default and in effect at all times.
5.6.2 Standby Blade
A Standby Blade is an extra RadioBlade transceiver that is installed in the system
but does not have a configured BR with which to register. To setup Standby
Blades, make sure that there are more RadioBlade transceivers for each DRBS
Group than Base Radios configured in the iDEN configuration page.
In all the conditions described below, if RadioBlade transceivers are present in the
system that are in the hot-standby state, then locking the RadioBlade transceiver
(due to alarms, removal of a RadioBlade transceiver or administratively locking
RadioBlade transceivers) will result in the hot Standby Blade transceiver being
assigned to the BR that de-registered the locked RadioBlade transceiver.
5.6.3 Locking Policy for RadioBlade Transceiver with Errors
If the RadioBlade transceiver generates enough faults such that it crosses the
Bounce and Duration threshold for that particular error, an alarm will be
generated. The RadioBlade controller then notifies the associated BR, which then
locks the RadioBlade transceiver. This will result in disabling the BR.
If there is a faulty RadioBlade transceiver in the system (generating error alarms),
it is prevented from coming up after a commanded reset/system reset, but the
operator could manually unlock the RadioBlade transceiver, at which point the
RadioBlade transceiver would be assigned to a BR. (This would not prevent the
system from locking it again if an excessive error condition recurs).