Change Note

8/22/2019 Change Note

http://slidepdf.com/reader/full/change-note 1/19

Change Note Forms

Id: CXM5 CD4.0Product Family: Base StationsProduct: Nokia MetroSite BTS Release: CXM5

©Nokia Siemens Networks Company Confidential 1 (19)



CN-id: 14002CNESPE01

Title:

8048 loss of incoming signal alarm is lost during BCF reset

Version of the SW-build:

CX5 CD4.0

Valid for Product(s):Nokia MetroSite EDGE

References:

Reason for the Change Note:

Original Problem:Site remains in UNSYNCH mode after LMU (master) reset is performed although LMUis up & working. Alarm 8048 remains active on BSC

Cause of the problem:On a BTS reset, its database gets reset. When during this reset the LMU sends acancel for 8048 alarm the BTS discards it because it searches for the correspondingStart of alarm which cannot found in its database. As a result of this the 8048 alarmremains active on BSC and site stays in UNSYCH mode

Which functionalities were affected by the problem:AH task in BTS SW is impacted

How end user/operator could detect the problem:It’s an occasionally seen problem. User can see that the site remains in UNSYCHmode although LMU is up.

Correction of the problem:For the 8000 series alarms no checking for start of alarm being present will beincluded.

Workaround:Site reset.

Configuration: Any configuration with LMU as the clock source.

< CXM5 CD4.0>




Corrected Fault Reports:

33787ES08P: 8048 loss of incoming signal alarm is lost during BCF reset

Modified components:

tah_send

CX5_CD4.0_OM_PR33787ES08P_BL001

Change effects:

Effects on Operator

Site recovers correctly to synchronised mode

Testing Instruct ions for the change

Pre-requirements:

All test cases are to be tested with LMUB (Midge).

All test cases should be performed using BSC SW S12 unless otherwise stated.

Test execution:

Test steps to reproduce the problem.

Input to Reproduce the Problem Expected Output

Configure the LMUB to a Q1 addressvalue of 131 at the BSC and with LMUmanager. Test with CXM4.1 CD4.0

LMUB gets configured to Q1 address 131.Clock source for the BTS is the LMUB.

Disconnect the Power cable and thenimmediately reconnect the Power cablefrom LMUB

LMU alarm 8048 loss of incoming signal alarm"START" gets reported on BTS Manager andBSC.BCF resets

GPS signal indicates “OK” then “LOCKED” onLMU managerLMU alarm 8048 loss of incoming signal alarm"CANCEL" gets reported on BTS Manager andnot the BSC during BCF reset.Site comes up to UNSYNC mode and will notrecover to LMU SYNC, because of 8048"CANCEL" having already been read during BCFstart-up. So BSC does not know that 8048 alarmis cancelled.

Case Ref. BCF Configuration

33787ES08P.01 4 TRX Omni MetroSite

< CXM5 CD4.0>




Test steps to verify the correction.

Input to Verify the Correction Expected Output

Configure the LMUB to a Q1 address value to131 at the BSC and with LMU manager. Test with CX5 CD4

LMUB gets configured to Q1 address 131.Clock source for the BTS is the LMUB.

Disconnect the Power cable and thenimmediately reconnect the Power cable fromLMUB

LMU alarm 8048 loss of incoming signalalarm "START" gets reported on BTSManager and BSC.BCF resetsGPS signal indicates “OK” then“LOCKED” on LMU managerLMU alarm 8048 loss of incoming signal

alarm "CANCEL" gets reported on BTSManager and BSC during BCF reset.BCF resetsClock signal indicates “ON” on LMUmanagerSite comes back to working state withLMU as master approximately 6 minutesafter GPS signal indicates “LOCKED” onLMU manager.

Case Ref. BCF Configuration

33787ES08P.02 4 TRX Omni MetroSite

Unexpected results :

The BTS does not recover in LMU sync mode after LMU has been reset. There areunexpected alarms following testing.

< CXM5 CD4.0>





Title:

Additional alarms to be displayed by BTS Manager


CXM5 CD4.0


References:


The following alarms are now displayed in BTS Manager

• 8202 Loss of supervision connection• 8240 Active alarm point• 8272 Position not locked• 8003 Loss of remote power supply• 8126 Unit function degraded• 8145 Temperature alarm



BTS Manager

Change effects:

Effects on end-user

The end user will observe that the alarms are now seen when using the BTS Managerapplication.

< CXM5 CD4.0>





Pre-requirements:

Note 1.

Unless otherwise indicated in the test case, set the LMU timer values as follows. UseLMU Manager (version 4.4 for LMU and version 1.0 CD3.0 for LMUB). Select View → Advanced. Select Maintenance. Open the “Clock Out Time Settings…” dialogue box.Set the Time from fix lost to clocks out alarm to 120 sec. Set the Time from clocks out

alarm to clock disable to 60 sec.

Note 2.

The BSC ‘Loss of LMU Sync Alarm Limit’ timer has been set up. Default value is 1 hour. The BSC ‘BCF Restarted due to Loss of LMU Sync’ timer has been set up. Defaultvalue is 24 hours.

Note 3.

The BSC values for the timers ‘Loss of LMU Sync Alarm Limit’(LMUSYN_LOSS_ALARM_LIMIT) and ‘BCF Restarted due to Loss of LMU Sync’(LMUSYN_LOSS_RESET_LIMIT) could be verified using the MML command,ZWOI:37;.

The values could then be modified to the required value using the MML command,ZWOC:37,<Identifier>,<value>;

Where:

• <identifier> = 43 for ‘Loss of LMU Sync Alarm Limit’ and 44 for ‘BCF Restarteddue to Loss of LMU Sync’

<value> = hex value for the number of hours needed e.g. 18 for 24 hours

< CXM5 CD4.0>




Test execution:

8202 LOSS OF SUPERVISION CONNECTION

Purpose: To verify that alarm “8202 LOSS OF SUPERVISION CONNECTION” isreported on BTS Manager.

BTS/Q1 IF

LMU

CABINET I/P

Q1

Figure 1.

Input Expected Output

Use BTS configuration as specified in test case. Site is in supervisory state.Monitor the alarms at BTS Manager and BSC. No unexpected alarms are seen at BSC and

BTS Manager.Remove the Q1[Figure 1] Interface cable towardsBTS.

Alarm “8202: Loss of Supervision Connection” isreported on BTS Manager and BSC.

Re-connect the Q1 Interface cable towards BTS. Alarm “8202: Loss of Supervision Connection” iscancelled on BTS Manager and BSC. All thefields in alarm description are reported correctly.

Save the Site Information file on the PC. Site Information file can be successfully savedon the PC.

Open the saved Site Information file and verify thealarms.

Site Information file is successfully opened andall the alarms as reported in BTS Manager arepresent in the Site Information file. All the fieldsin alarm description are reported correctly.

Calls are made on all TRX. All calls are successful

CaseRef.

BTS Configuration LMU Type BTS Manager connection

1. 4 Omni, GSM MetroSite LMUB Local

2. 2 Omni, EDGE MetroSite LMU Remote

< CXM5 CD4.0>




8240 ACTIVE ALARM POINTPurpose: To verify that alarm “8240 ACTIVE ALARM POINT” is reported on BTSManager.

References to Requirement Documents

Note 4.

EAC inputs are defined to map transmission unit alarms, configure EAC input line asstated in test case.


Use BTS configuration as specified in test case. Site is in supervisory state.Monitor the alarms at BTS Manager & BSC. No unexpected alarms are seen at BSC and

BTS Manager.Use BSC MML command ZEFX:<BCFID>:INBR=1:ROU=TMS,POL=OPEN; to set basecontrol function external input parameters.

Base control function external input parametercan be defined successfully.

Use EAC alarm line to generate 8240 alarm. Alarm “8240: Active alarm point” is reported onBTS Manager and BSC.

Use EAC alarm line to cancel 8240 alarm. Alarm “8240: Active alarm point” is cancelled onBTS Manager and BSC.

Check the alarm description for start and cancel of 8240 alarm on BTS Manager.

All the fields in alarm description are reportedcorrectly in both start and cancel.


CaseRef.

BTS Configuration TransmissionCard

BTS Manager connection

3. 4 Omni, GSM MetroSite FXC E1/T1 Local

< CXM5 CD4.0>




8003 LOSS OF REMOTE POWER SUPPLYPurpose: To verify that alarm “8003 LOSS OF REMOTE POWER SUPPLY” isreported on BTS Manager.

Note 5.

All test cases for generating alarm “8003 LOSS OF REMOTE POWER SUPPLY” will beexecuted using a variable DC power supply up to 60V (48V nominal) output in 0.5Vsteps as follows

- for LMU: Operating Voltage 39 to 60 V(DC)

- for LMUB: Operating Voltage 36 to 60 V(DC)Note 6.

Operating Voltage for both LMU and LMUB is 48 V (DC)



BTS Manager.Reduce the supply voltage for LMU at the rate of 0.5V per minute until alarm “8003: Loss of Remote

Power Supply” is reported.

Alarm “8003: Loss of Remote Power Supply” isreported on BTS Manager and BSC.

Monitor the alarms at BTS Manager & BSC. Alarm “8003: Loss of Remote Power Supply”, isreported on BTS Manager and BSC.

Check the alarm description for start of 8003 alarmon BTS Manager.

All the fields in alarm description are reportedcorrectly.

Increase the supply voltage for LMU at the rate of 0.5V per minute until alarm “8003: Loss of RemotePower Supply” is cancelled.

Alarm “8003: Loss of Remote Power Supply” iscancelled on BTS Manager and BSC.


CaseRef.


4.4 Omni, GSM MetroSite LMUB Remote

5. 4 Omni, EDGE MetroSite LMU Local

< CXM5 CD4.0>




8272 POSITION NOT LOCKED

Purpose: To verify that alarm “8272 POSITION NOT LOCKED” is reported on BTSManager.



BTS Manager.Launch LMU Manager and connect to LMU. LMU Manager is launched and connected to

LMU successfully.Start “Commissioning Wizard” from LMU Manager. “Commissioning Wizard” is started successfully

from LMU Manager.Select “Start Self Survey after next reset” onsecond page of commissioning wizard andcomplete the commissioning.

“Start Self Survey after next reset” is selectedsuccessfully and commissioning can beperformed successfully.LMU is reset.

Monitor the alarms at BTS Manager & BSC. Alarm “8202: Loss of Supervision Connection”,“8048: Loss of Incoming Signal” and “7602 BCFNotification. Base Station Synchronisationfailed” is reported on BTS Manager and BSC.BCF goes into BL-BCF state and the site isreset and comes into working state.

Check the clock synchronisation status of site afterreset at BSC & BTS Manager.

Site comes to supervisory state in unsyncmode.

Check LMU Manager for GPS fix. GPS Fix shows "OK (Survey) [xx%]Monitor the alarms at BTS Manager & BSC. Alarm “8272: Position not locked”, “8202: Loss

of Supervision Connection”, “8048: Loss of Incoming Signal” and “7602 BCF Notification.Base Station Synchronisation failed” is reportedon BTS Manager and BSC. In alarm descriptionLMU is reported correctly.Site resets when clock output is “ON” and 8048and 7602 alarms are cancelled.

Monitor the LMU Manager for “GPS fix =OK (Locked)”

Alarm “8272: Position not locked” is cancelledwhen “GPS fix =OK (Locked)” on BTS Manager& BSC.It may take 24 hrs or more for GPS fix to belocked.

Save the Site Information file on the pc. Site Information file can be successfully saved

on the PC.Open the save Site Information file and verify thealarms.

Site Information file is successfully opened andall the alarms as reported in BTS Manager arepresent in the Site Information file. All the fieldsin alarm description are reported correctly inboth start and cancel.


CaseRef.

BTS Configuration LMU BTS Manager connection

6. 4+4, GSM+EDGE MetroSite LMUB Local

7. 2 Omni, EDGE MetroSite LMUB Remote

< CXM5 CD4.0>




Compatibility of Previous BTS Manager with New BTS SW.

Purpose: To verify that Previous BTS Manager is compatible with new BTS SW.

Note 7.

All test cases in this section are required to be executed with SiteWizard 5 CD3.0BTSManager (or earlier) and BTS SW CXM5 CD4.0.

< CXM5 CD4.0>




Input Expected OutputUse BTS configuration as specified in test case. Site is in supervisory state.Monitor the alarms at BTS Manager & BSC. No unexpected alarms are seen at BSC and

BTS Manager.Launch LMU Manager and connect to LMU. LMU Manager is launched and connected to

LMU successfully.Start “Commissioning Wizard” from LMU Manager. “Commissioning Wizard” is started successfully

from LMU Manager.Select “Start Self Survey after next reset” onsecond page of commissioning wizard andcomplete the commissioning.

“Start Self Survey after next reset” is selectedsuccessfully and commissioning can beperformed successfully.LMU is reset.

Monitor the alarms at BTS Manager. Alarm “8202: Unknown alarm (8202)”, “8048:Loss of Incoming Signal” and “7602 BCFNotification. Base Station Synchronisationfailed” is reported on BTS Manager.BCF goes into BL-BCF state and the site isreset and comes into working state.

Check the clock synchronisation status of site afterreset at BSC & BTS Manager.

Site comes to supervisory state in unsyncmode.

Check LMU Manager for GPS fix. GPS Fix shows "OK (Survey) [xx%]Monitor the alarms at BTS Manager. Alarm “8272: Unknown alarm (8272)”, “8202:

Unknown alarm (8202)”, “8048: Loss of Incoming Signal” and “7602 BCF Notification.Base Station Synchronisation failed” is reported

on BTS Manager. In alarm description LMU isreported correctly.Site resets when clock output is “ON” and 8048and 7602 alarms are cancelled.

Monitor the LMU Manager for “GPS fix =OK (Locked)”

Alarm “8272: Unknown alarm (8272)” iscancelled when “GPS fix =OK (Locked)” onBTS Manager.It may take 24 hrs or more for GPS fix to belocked.


Open the save Site Information file and verify thealarms.

Site Information file is successfully opened andall the alarms as reported in BTS Manager are

present in the Site Information file. All the fieldsin alarm description are reported correctly inboth start and cancel.


CaseRef.

BTS Configuration LMU BTS Manager connection

8. 4 Omni, EDGE MetroSite LMUB Local

< CXM5 CD4.0>




Input Expected OutputUse BTS configuration as specified in test case. Site is in supervisory state.Monitor the alarms at BTS Manager & BSC. No unexpected alarms are seen at BSC and

BTS Manager.Reduce the supply voltage for LMU at the rate of 0.5V per minute until alarm “8003: Unknown alarm(8003)” is reported.

Alarm “8003: Unknown alarm (8003)” isreported on BTS Manager.

Check the alarm description for start of 8003 alarmon BTS Manager.

All the fields in alarm description are reportedcorrectly.

Increase the supply voltage for LMU at the rate of 0.5V per minute until alarm “8003: Unknown alarm(8003)” is cancelled.

Alarm “8003: Unknown alarm (8003)” iscancelled on BTS Manager.


Open the saved Site Information file and verify thealarms.

Site Information file is successfully opened andall the alarms as reported in BTS Manager arepresent in the Site Information file. All the fieldsin alarm description are reported correctly.


CaseRef.


9. 4 Omni, EDGE MetroSite LMU Local

< CXM5 CD4.0>





Title:

MetroSite does not recover from a site reset during a Remote Manager session


CXM5 CD4.0


References:


Original Problem:On connecting LMU Manager in remote and BTS Manager in local, site doesn’trecover when reset. Continuous resets are triggered.

Cause of the problem:Messages exchanged between LMU, BTS and BSC.

Which functionalities were affected by the problem:Reset of site

How end user/operator could detect the problem:On reset of site when one remote connection and one local connection are running inparallel the site does not recover to a working state.

Workaround:Close one of the connections.

Configuration:LMU - Metro.


14170ES10P: MetroSite does not recover from Site Reset when a Remote Managersession is active

Modified components: The problem does not occur with current versions of the SW following generalimprovements to message timing in O&M SW.

Effects on Operator Simultaneous connection of LMU Manager and BTS Manager is now possible

< CXM5 CD4.0>





Pre-requisites:

Site is a slave MetroSite with a LMU as the clock master.

Sector TRX

ETRX 1

ETRX 2 (BCCH)

ETRX 3

1

ETRX 4

NB: issue is not band specific.

Test execution:

BTS Software: (a) CXM4 CD2.0(b) CXM5 CD4.0

Precondition: The site is in supervisory state.

Teststep

Test Step Instructions Output Comments

1Connect the LMU Managerremotely to the BTS Site.

LMU Manager is remotelyconnected

This is the expectedbehaviour

2Connect BTS Manager to the sitelocally.

BTS Manager shows all the TRXand their current state.

This is the expectedbehaviour.

3Give the site a local reset fromthe BTS Manager Site takes a reset This is the expected

behaviour

4aWait for the site to come up inthe working state.

Site comes up in working stateand the goes into continuousresets.

This is not the expectedbehaviour

4b Wait for the site to come up inthe working state.

Site comes up in working statenormally

This is the expectedbehaviour

< CXM5 CD4.0>





Title:

BCCH transmission activated in chained slave sector after enabling STIRC


CXM5 CD4.0


References:


Summary of the original problem:Using a chained 4+4+4 non-EDGE MetroSite, TRX 9 is configured as the BCCH TRX.When STIRC is enabled for the third sector the following alarms are reported correctly:

7606 “TRX FAULTY: Non EDGE TRX device type used accidentally in Edge CapableMode” against TRX 9, 10 and 11

7603 "BTS FAULTY: Non EDGE TRX device type used accidentally in Edge CapableMode" against BTS 3

However, after the 7603 sector alarm is raised, TRX 12 continues transmitting theBCCH indefinitely, which is not expected behaviour.

How end user/operator could detect the problem:BCCH is broadcast on a 7606 TRX Faulty TRX, in a 7603 BTS Faulty sector. This is ahealth and safety issue.

Description of the fault:BCCH is not stopped correctly when the TRX alarms because of incompatibility non-EDGE TRX enabled for STIRC.

Related feature / functionality:Alarm handling has been improved.

Dependency on configuration:non-EDGE hardware

Workaround:none

Description of the correction: The timeout covering TRX initialisation has been extended to ensure that stopping theBCCH transmission is the last action.

Effects on end-user:BCCH stops as expected.

< CXM5 CD4.0>




Effects on operator:

None.

Faulty component and version:tah_comm.h cx5cd3_om_me_b004#1

Faulty component first delivered in (e.g. release, CD):CXM5 CD3.0


5984C02 : BCCH transmission from GSM slave sector in MetroSite chain afterenabling STIRC


tah_comm

cx5cd3_om_me_b008#2

Change effects:

Effects on end-user None

Effects on Operator Operation of BTS is safer for maintenance personnel

< CXM5 CD4.0>





Pre-requisites:A MetroSite is configured as 4+4+4 non-EDGE The MetroSite is in supervisory state with TRX 9 set as a BCCH. A Spectrum analyser is connected to TRX 12.

BTS SW (a) CXM5 CD3.0(b) CXM5 CD4.0

Test execution:

Teststep

Test Step Instructions Expected Resul t

1aEnable STIRC for the third sectorusing MML command ZEQM

Alarm 7606 "TRX FAULTY: Non EDGE TRX devicetype used accidentally in Edge Capable Mode" is

reported for TRX 9, 10, & 11 and these TRX are in BL- TRX state at BSC after reconfiguration.Alarm 7603 "BTS FAULTY: Non EDGE TRX device typeused accidentally in Edge Capable Mode" is reported forthird sector and BTS is in BL-BTS state at BSC. TRX 12 keeps transmitting BCCH as seen on thespectrum analyser. This is the unwanted behaviour.

The MetroSite is in supervisory state. TRX 1 is set as the BCCH and a spectrum analyser is connectedto TRX 4

Teststep


1bEnable STIRC for the first sector usingMML command ZEQM.

Alarm 7606 "TRX FAULTY: Non EDGE TRXdevice type used accidentally in Edge CapableMode" is reported for TRX 1, 2, & 3 which are inBL-TRX state at BSC after reconfiguration.Alarm 7603 "BTS FAULTY: Non EDGE TRXdevice type used accidentally in Edge CapableMode" is reported for first sector and BTS is in BL-BTS state at BSC.Within 30 seconds of 7603 alarm, TRX 4 stopstransmitting the BCCH and does not restart, asseen on the spectrum analyser.

2Repeat Step 1 with the BCCH TRXpreconfigured as TRX 2, 3, and 4.

Within 30 seconds of 7603 alarm, TRX 4 stopstransmitting the BCCH and does not restart, as

seen on the spectrum analyser.

3

With the spectrum analyser connectedto TRX 8 and the BCCH preconfiguredon TRX 5, enable STIRC for the secondsector using MML command ZEQM.

Alarm 7606 "TRX FAULTY: Non EDGE TRXdevice type used accidentally in Edge CapableMode" is reported for TRX 5, 6, & 7 which are inBL-TRX state at BSC after reconfiguration.Alarm 7603 "BTS FAULTY: Non EDGE TRXdevice type used accidentally in Edge CapableMode" is reported for second sector and BTS is inBL-BTS state at BSC.Within 30 seconds of 7603 alarm, TRX 8 stopstransmitting the BCCH and does not restart, asseen on the spectrum analyser.

4

Repeat Step 3 with the BCCH TRX

preconfigured as TRX 6, 7, and 8.

Within 30 seconds of 7603 alarm, TRX 8 stops

transmitting the BCCH and does not restart, asseen on the spectrum analyser.

< CXM5 CD4.0>




5

With the spectrum analyser connectedto TRX 12 and the BCCH preconfiguredon TRX 9, enable STIRC for the secondsector using MML command ZEQM.

Alarm 7606 "TRX FAULTY: Non EDGE TRXdevice type used accidentally in Edge Capable

Mode" is reported for TRX 9, 10, & 11 which arein BL-TRX state at BSC after reconfiguration.Alarm 7603 "BTS FAULTY: Non EDGE TRXdevice type used accidentally in Edge CapableMode" is reported for third sector and BTS is inBL-BTS state at BSC.Within 30 seconds of 7603 alarm, TRX 12 stopstransmitting the BCCH and does not restart, asseen on the spectrum analyser.

6Repeat Step 5 with the BCCH TRXpreconfigured as TRX 10, 11, and 12.

Within 30 seconds of 7603 alarm, TRX 12 stopstransmitting the BCCH and does not restart, asseen on the spectrum analyser.

Test descriptionVerify Local Blocking functions correctly.

Test steps & expected resultsPrecondition: MetroSite is in supervisory state. TRX 9 is set as BCCH.

Teststep


1 Block TRX 9 The BCCH is reconfigured to TRX 10. Calls canbe made in the third sector.

2Block TRX 10 The BCCH is reconfigured to TRX 11. Calls can

be made in the third sector.

3Block TRX 11 The BCCH is reconfigured to TRX 12. Calls can

be made in the third sector.

Unexpected results :BCCH continues to be transmitted.

Change Note

Documents

Transcript of Change Note