carrier tx and rx power alarms

48-2 PM (RCU) MONortel Networks Confidential Copyright 1997–2003 Nortel Networks

NN-20000-901 Standard 01.13 October 2003

CarrierRx0Power measured is too high 48Summary informationDiagnostic Code Hexadecimal 743cDiagnostic Code Decimal 29756Alarm Type EquipmentPerceived Severity Major

DescriptionThis is an indication that the Rx0 estimate of received power is outside (too high) the range specified in the SectorRxPowerFaultThresholds attribute.

Impact to system operationPower management operation failure.

Possible causes1. External interference caused by

– AMPS mobile from a bordering SID with the same frequency as the CDMA Carrier. This can occur if the CDMA spectrum is not cleared out sufficiently around the CDMA service area. It can also be caused by a mobile that is contacting its home cell (not roaming) with a booster. It can also be caused by a malfunctioning mobile.

– CDMA mobile with a homemade booster which swamps out other users.

– by bad cables on the transmitters causing an intermittent connection leading to the generation of spectral splatter.

2. Incorrect cabling configuration.

3. DPM or TRM receive calibration error.

4. Hardware failure.

Recommended response1. Use a spectrum analyzer to verify if the alarm is due to external

interference. In most cases the alarm clears without any intervention after the interference has moved on.

2. Ensure proper cabling configuration.

3. If alarm persists, replace DPM.

4. If alarm persists, replace TRM.

PM (RCU) MO 48-3Nortel Networks Confidential Copyright 1997–2003 Nortel Networks

CDMA Fault Management: Alarms Reference Manual NBSS 11.0

CarrierRx0Power measured is too low 48Summary informationDiagnostic Code Hexadecimal 743bDiagnostic Code Decimal 29755Alarm Type EquipmentPerceived Severity Major

DescriptionThis is an indication that the Rx0 estimate of received power is outside (too low) the range specified in the SectorRxPowerFaultThresholds attribute.


Possible causes1. DPM Rx signal path failure (LNA or internal connectors).

2. DPM to TRM Rx cable or connector failure.

3. TRM Rx signal path failure.

4. Water intrusion in the connections.

5. Failed LNA.

Recommended response1. Verify Rx cables are installed correctly and connectors are well-seated

and torqued to specifications.

2. Remove and inspect connectors on the failed side for evidence of water intrusion.

3. Replace DPM if a LNA fault is also active.



CarrierRx1Power measured is too high 48Summary informationDiagnostic Code Hexadecimal 743eDiagnostic Code Decimal 29758Alarm Type EquipmentPerceived Severity Major

DescriptionThis is an indication that the Rx1 estimate of received power is outside (too high) the range specified in the SectorRxPowerFaultThresholds attribute.


Possible causes1. External interference caused by

– AMPS mobile from a bordering SID with the same frequency as the CDMA Carrier. This can occur if the CDMA spectrum is not cleared out sufficiently around the CDMA service area. It can also be caused by a mobile that is contacting its home cell (not roaming) with a booster. It can also be caused by a malfunctioning mobile.

– CDMA mobile with a homemade booster which swamps out other users.

– bad cables on the transmitters causing an intermittent connection leading to the generation of spectral splatter.

2. Incorrect cabling configuration.

3. DPM or TRM receive calibration error.

4. Hardware failure.

Recommended response1. Use a spectrum analyzer to verify if the alarm is due to external

interference. In most cases the alarm clears without any intervention after the interference has moved on.

2. Ensure proper cabling configuration.

3. If alarm persists, replace DPM.

4. If alarm persists, replace TRM.



CarrierRx1Power measured is too low 48Summary informationDiagnostic Code Hexadecimal 743dDiagnostic Code Decimal 29757Alarm Type EquipmentPerceived Severity Major

DescriptionThis is an indication that the Rx1 estimate of received power is outside (too low) the range specified in the SectorRxPowerFaultThresholds attribute.


Possible causes1. DPM Rx signal path failure (LNA or internal connectors).

2. DPM to TRM Rx cable or connector failure.

3. TRM Rx signal path failure.

4. Water intrusion in the connections.

5. Failed LNA.

Recommended response1. Verify Rx cables are installed correctly and connectors are well-seated

and torqued to specifications.

2. Remove and inspect connectors on the failed side for evidence of water intrusion.

3. Replace DPM if a LNA fault is also active.



CarrierRxPowerDiff measured is too high - Rx0 higher 48Summary informationDiagnostic Code Hexadecimal 743fDiagnostic Code Decimal 29759Alarm Type EquipmentPerceived Severity Major

Example

“0%: CBS1:Cells1:MC1900BTS6:MCBTSSubsystem1:Root1:BTSCallProcessing1:AdvancedFA1:AdvancedSector1: PowerManagement1” MAJOR “SectorRxPowerDiff measured is too high - Rx0 higher // RCUMO Fault” AlarmType=Equipment DiagnosticCode=29835

DescriptionThis fault indicates that the Rx0 power is 240dBfw*16 higher than the Rx1 power for 10 consecutive (BBWStepPeriod) 100 millisecond samples. The alarm clears when the difference between Rx0 and Rx1 drops below 240dBfw*16 for 10 consecutive (BBWStepPeriod) 100 millisecond samples.

Impact to system operationPotential call performance degradation as one Rx path may have degraded/failed or may be experiencing external interference.

Possible causes1. Normal RF propagation differences between Rx0 and Rx1, which could

be caused by deep fading of one of the antennas.

2. Metro Cells initially installed with just the main antenna attached, with the receive diversity antenna being attached later.

3. A change in the gain of one of the receiver chains (this would also trigger a Rx low power alarm):

— DPM/ Triplexor signal path failure

— DPM/ Triplexor to TRM cabling failure

— splitter failure (800Mhz)

— TRM Rx path component failure

— hardware failure in donor RFM (in multi-carrier configurations)

4. Faulty or incorrect cabling between (this would also trigger a Rx low power alarm)

— antenna and DPM/Triplexor input (antenna jumper)

— DPM and splitter(800Mhz multi-carrier)

— splitter and TRM(800Mhz multi-carrier)



— DPM/Triplexor and TRM(1900Mhz multi-carrier)

— donor TRM and TRM (early multi-carrier configurations where an external splitter or triplexor was not used)

5. Incorrect datafill of the following PowerManagement MO attribute(s):

• 7.1.2x releases

— Rx1DPMInstalled

– should be set to True if the DPM in the RFM is providing both the main and diversity Rx paths.

– should be set to False if the DPM in the RFM is only providing the main Rx path. This enables to PowerBalancing algorithm to run when the PowerManagement MO is initialized.

• 8.1 and later releases.

— DPMRxConfig

– should be set to 0x01 if the DPM in the RFM is providing both the main and diversity Rx paths.

– should be set to 0x02 if the DPM in the RFM is only providing the main Rx path. The software runs the PowerBalancing algorithm on PowerManagement MO initialization. This requires that the Rx paths be terminated for correct balancing.

– should be set to 0x03 if the DPM in the RFM is using the diversity DPM path to provide the main Rx path to the TRM. (This is basically used to have the Tx and Rx on separate antennas versus duplexing them on to one). The software runs PowerBalancing algorithm on PowerManagement MO initialization. This requires that the Rx paths be terminated for correct balancing.

– should be set to 0x00 if no DPM is provided.

— Rx0GainOffset

– should be datafilled to include the path loss between the DPM and the TRM. This accounts for any splitter/cabling/configuration changes between the DPM and the TRM. For example, splitters are added between the DPM and TRM on both the main and diversity paths. The DPMRxConfig attribute should be set to 0x02. Customer supplied DPM/LNA/Filters should also be accounted for.

– should be datafilled with all DPMRxConfig values if external customer test equipment is put between the DPM and the TRM.

— Rx1GainOffset

– should be datafilled to include the path loss between the DPM and the TRM. The DPMRxConfig attribute should be set to 0x02 if



any customer supplied equipment is used in place of or in addition to Nortel equipment.


Recommended response1. Identify which Rx path is likely to be faulty. This is done by checking

both the SectorRxPower0 attribute and SectorRxPower1attribute. The Rx path with power reported within +/- 3dB of the nominal value is correct. The other Rx path is faulty.

Note 1: Under steady state, that is, with no calls, both Rx0 and Rx1 are close. If not, then this is an indication of a problem between the DPM (inclusive) and the TRM. When calls are applied to the system, one of the paths changes radically while the other path remains the same. The faulty path can be identified by logging the SectorRxPowerLog in the PowerManagement MO during the time period when the alarm happens.

Note 2: Nominal value for a sector with no calls is 98 to 216 dBfW*16 (this range is for 800Mhz, 1900Mhz, and non-Extended/Rural Cell, and is dependent on measurement accuracy. For Extended/Rural cell sites, the value would be offset by the gain of the customer provided LNA).

Note 3: performing a “ls -f” on the PowerManagement MO SectorRx0Power and SectorRx1Power attributes does not provide adequate information to troubleshoot this alarm

2. If the power of the faulty Rx path is too low follow the recommended response section of the SectorRx Power measured is too low alarm.

3. If the power of the faulty Rx path is too high follow the recommended response section of the SectorRx Power measured is too high alarm.

Note 4: Before any Metro Cells are put in-service, ensure that all receive antenna cables, main and diversity, are connected. The PowerBalancing algorithm should be run to balance the gains.

4. Initialize the RFM.

5. Check for faulty or incorrect cabling.



CarrierRxPowerDiff measured is too high - Rx1 higher 48Summary informationDiagnostic Code Hexadecimal 7440Diagnostic Code Decimal 29760Alarm Type EquipmentPerceived Severity Major

DescriptionThis fault indicates that the Rx1 power is 240dBfw*16 higher than the Rx1 power for 10 consecutive (BBWStepPeriod) 100 millisecond samples. The alarm clears when the difference between Rx0 and Rx1 drops below 240dBfw*16 for 10 consecutive (BBWStepPeriod) 100 millisecond samples.

Impact to system operationPotential call performance degradation as one Rx path may have degraded/failed or may be experiencing external interference.

Possible causes1. Normal RF propagation differences between Rx0 and Rx1, which could

be caused by deep fading of one of the antennas.

2. Metro Cells initially installed with just the main antenna attached, with the receive diversity antenna being attached later.

3. A change in the gain of one of the receiver chains (this would also trigger a Rx low power alarm):

— DPM/ Triplexor signal path failure

— DPM/ Triplexor to TRM cabling failure

— splitter failure (800Mhz)

— TRM Rx path component failure

— hardware failure in donor RFM (in multi-carrier configurations)

4. Faulty or incorrect cabling between (this would also trigger a Rx low power alarm)

— antenna and DPM/Triplexor input (antenna jumper)

— DPM and splitter(800Mhz multi-carrier)

— splitter and TRM(800Mhz multi-carrier)

— DPM/Triplexor and TRM(1900Mhz multi-carrier)

— donor TRM and TRM (early multi-carrier configurations where an external splitter or triplexor was not used)

5. Incorrect datafill of the following PowerManagement MO attribute(s):

• 7.1.2x releases



— Rx1DPMInstalled

– should be set to True if the DPM in the RFM is providing both the main and diversity Rx paths.

– should be set to False if the DPM in the RFM is only providing the main Rx path. This enables to PowerBalancing algorithm to run when the PowerManagement MO is initialized.

• 8.1 and later releases.

— DPMRxConfig

– should be set to 0x01 if the DPM in the RFM is providing both the main and diversity Rx paths.

– should be set to 0x02 if the DPM in the RFM is only providing the main Rx path. The software runs the PowerBalancing algorithm on PowerManagement MO initialization. This requires that the Rx paths be terminated for correct balancing.

– should be set to 0x03 if the DPM in the RFM is using the diversity DPM path to provide the main Rx path to the TRM. (This is basically used to have the Tx and Rx on separate antennas versus duplexing them on to one). The software runs PowerBalancing algorithm on PowerManagement MO initialization. This requires that the Rx paths be terminated for correct balancing.

– should be set to 0x00 if no DPM is provided.

— Rx0GainOffset

– should be datafilled to include the path loss between the DPM and the TRM. This accounts for any splitter/cabling/configuration changes between the DPM and the TRM. For example, splitters are added between the DPM and TRM on both the main and diversity paths. The DPMRxConfig attribute should be set to 0x02. Customer supplied DPM/LNA/Filters should also be accounted for.


— Rx1GainOffset

– should be datafilled to include the path loss between the DPM and the TRM. The DPMRxConfig attribute should be set to 0x02 if any customer supplied equipment is used in place of or in addition to Nortel equipment.




Recommended response1. Identify which Rx path is likely to be faulty. This is done by checking

both the SectorRxPower0 attribute and SectorRxPower1attribute. The Rx path with power reported within +/- 3dB of the nominal value is correct. The other Rx path is faulty.

Note 1: Under steady state, that is, with no calls, both Rx0 and Rx1 are close. If not, then this is an indication of a problem between the DPM (inclusive) and the TRM. When calls are applied to the system, one of the paths changes radically while the other path remains the same. The faulty path can be identified by logging the SectorRxPowerLog in the PowerManagement MO during the time period when the alarm happens.

Note 2: Nominal value for a sector with no calls is 98 to 216 dBfW*16 (this range is for 800Mhz, 1900Mhz, and non-Extended/Rural Cell, and is dependent on measurement accuracy. For Extended/Rural cell sites, the value would be offset by the gain of the customer provided LNA).

Note 3: performing a “ls -f” on the PowerManagement MO SectorRx0Power and SectorRx1Power attributes does not provide adequate information to troubleshoot this alarm

2. If the power of the faulty Rx path is too low follow the recommended response section of the SectorRx Power measured is too low alarm.

3. If the power of the faulty Rx path is too high follow the recommended response section of the SectorRx Power measured is too high alarm.

Note 4: Before any Metro Cells are put in-service, ensure that all receive antenna cables, main and diversity, are connected. The PowerBalancing algorithm should be run to balance the gains.

4. Initialize the RFM.

5. Check for faulty or incorrect cabling.



CarrierTxPower measured is too low 48Summary informationDiagnostic Code Hexadecimal 7445Diagnostic Code Decimal 29765Alarm Type EquipmentPerceived Severity Major

DescriptionTx power is too low.


Possible causesUpconverter hardware components or HPA failure.

Recommended responseCheck connection between TRM and PAM.

carrier tx and rx power alarms

Documents