RadioFrame Networks Inc MCSERIESHP10 User Manual
Scheduled and Unscheduled Maintenance
MC-Series High-Power System
998--01
Rev
X1
82
CONFIDENTIAL AND PROPRIETARY
RadioFrame Networks, Inc.
TRADE SECRET INFORMATION
Tx Overflow
RadioBlade transceiver received too many packets to transmit.
Rx OverFlow
Sample buffer overflowed.
Slot mismatch
Received packets were not consecutive.
CRC errors
Received Ethernet packets had CRC errors.
If a RadioBlade transceiver generates enough errors such that it crosses the Bounce and
Duration threshold for that particular error, an alarm will be generated. This alarm will also
cause the RadioBlade Locking Policy to lock that RadioBlade transceiver. Table 29 lists
the fault count and fault period for an alarm to be generated.
Duration threshold for that particular error, an alarm will be generated. This alarm will also
cause the RadioBlade Locking Policy to lock that RadioBlade transceiver. Table 29 lists
the fault count and fault period for an alarm to be generated.
Table 29 RadioBlade Transceiver Fault Thresholds for Alarm Generation
Alarm
Bounce Threshold
(counts)
Duration Threshold
(minutes)
PLL 1
75
12
PLL 2
75
12
PLL 3
50
12
Tx Underrun
40
12
Tx Overflow
40
12
Rx Overflow
40
12
Slot Mismatch
40
12
CRC Errors
20
12
Packet Size Errors
20
12
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.
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.
7.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).
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.)
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.
7.6.1.1 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 RBS Group than Base Radios
configured in the iDEN configuration page.
does not have a configured BR with which to register. To setup Standby Blades, make
sure that there are more RadioBlade transceivers for each RBS Group than Base Radios
configured in the iDEN configuration page.