RadioFrame Networks Inc MCSERIESHP10 User Manual
MC-Series High-Power System
Scheduled and Unscheduled Maintenance
998--01 Rev X1
RadioFrame Networks, Inc.
CONFIDENTIAL AND PROPRIETARY 81
Event
Description
Advisor
Site Service call
Comments None
Alert Names
BREFCTLBD35009
Last updated
8/3/2001
Revision
Change Notes
8/3/2001: per new EBTS rules baseline.
Changed severity and threshold from GR1 to:
Severity=minor
BounceThreshold=3
Bounce Threshold Minutes=30
Duration Threshold=10
Changed severity and threshold from GR1 to:
Severity=minor
BounceThreshold=3
Bounce Threshold Minutes=30
Duration Threshold=10
Action Create
trouble
ticket.
Contact Field Technician.
TS/BR
TS/BR
7.5.3 System Manager Alarms
The document Alarms/Events Reference Guide lists MC-Series system alarms
numerically by alarm ID (0x01, 0x02, etc.).
numerically by alarm ID (0x01, 0x02, etc.).
MC-Series alarms are based on the X.733 conventions for telecommunications
equipment. The alarms are grouped by service: either “asp” for platform faults or “iden”
for iden application faults. The “cause” field contains the X.733 cause type. “System
reaction” describes the action taken by the system as a result of this alarm, and “repair
actions” provides details on what corrective action should be taken as a result of this
alarm.
equipment. The alarms are grouped by service: either “asp” for platform faults or “iden”
for iden application faults. The “cause” field contains the X.733 cause type. “System
reaction” describes the action taken by the system as a result of this alarm, and “repair
actions” provides details on what corrective action should be taken as a result of this
alarm.
The Alarm details on the active alarm manager page of System Manager provides
additional information with respect to the board, slot number, MAC address and
equipment type.
additional information with respect to the board, slot number, MAC address and
equipment type.
7.6 RadioBlade Transceiver Alarm Handling
The iDEN RadioBlade transceivers track various faults and reports to the RadioBlade
controller. These faults are monitored, and if the rate at which these faults occur
surpasses a threshold, the RadioBlade transceiver (blade) is locked. The blade will
generate these faults as the result of normal actions such as re-syncing the blade, locking
and unlocking the blade and locking and unlocking the BR. For these reasons, only if the
blade continues to generate these faults under normal operating circumstances is an
alarm generated.
controller. These faults are monitored, and if the rate at which these faults occur
surpasses a threshold, the RadioBlade transceiver (blade) is locked. The blade will
generate these faults as the result of normal actions such as re-syncing the blade, locking
and unlocking the blade and locking and unlocking the BR. For these reasons, only if the
blade continues to generate these faults under normal operating circumstances is an
alarm generated.
The RadioBlade transceiver tracks the faults listed in Table 28.
Table 28 Faults Tracked by the Transceiver
Fault
Description
PLL1 Errors
The Phase Lock Loop #1 went out of lock.
PLL2 Errors
The Phase Lock Loop #2 went out of lock.
PLL3 Errors
The Phase Lock Loop #3 went out of lock.
Tx Underrun
RadioBlade transceiver did not receive a packet in time to transmit.