20 Sites IPPM Active Apr6 To Apr7

AT&T NETWORK
20 sites IPPM active
Prepared by:
LIYANLONG
Date:
Reviewed by:
Date:
Approved by:
Date:
6-4-2016
Implementation Solution for Change
CONTENT
Description of Change
1.1
Description of Sites.................................................................................................4
1.2
Purpose....................................................................................................................4
1.3
Description of Change and Change Influence........................................................4
1.4
License should be apply before a week..................................................................6
1.5
Version information................................................................................................6
1.6
Impact on the System During the Adjustment........................................................6
1.7
Equipment Running Check.....................................................................................6
Preparations for Change

2.1
During 00:00 8th to 23:00 8th Sep, we need to ask customer stop any operation
with this two RNCs.....................................................................................................................7
2.2
Change Period.........................................................................................................7
2.3
Composition of Change Team and Responsibility of Team Members...................7
2.2.1
Change Team of Huawei Company..............................................................................7
2.2.2
Huawei On-site Monitoring Team................................................................................7
2.2.3
Huawei Support & Guarantee Team............................................................................7
2.4
Change Risks and Countermeasures.......................................................................8
2.5
Check Before Change.............................................................................................8
Procedure
11
3.1
Operation Steps for Change..................................................................................11
3.2
Back up.................................................................................................................12
3.3
Change Period.......................................................................................................15
3.4
Change step and operation....................................................................................15
Verifying the operation
17
4.1
Check the RNC MOCN script have already configured successfully..................17
4.2
Check Alarms after adjustment and ensure no related alarms to this activity......18
4.3
Monitor KPIs........................................................................................................18
Rollback
19
5.1
Rollback Responsibility........................................................................................19
5.2
Overall Description of rollback............................................................................19
5.3
Rollback Procedure...............................................................................................19
5.4
Definition of change failure..................................................................................20
Technical support website:

http://support.huawei.com
Page 2 of 16
5.5
Information Collection Before rollback...............................................................20
5.6
Change back steps.................................................................................................20
5.7
Tests after Change back........................................................................................22
5.7.1
After roll back, check RNC and NODEB cells status normal or not...................22
5.7.2
Check if any new alarms come out.......................................................................24
5.7.3
Check the service on site for RNC users runs well..............................................24
5.7.4
Monitor KPIs........................................................................................................24
5.8
Change back Risk analysis...................................................................................24
Resources

25
Page 3 of 16
1 Description of Change
1.1
Description of Sites
Mexico city 20 sites need active IPPM to check the transmission
1.2
Purpose
Activate IPPM of 20 sites to check the transmission.
1.3
Description of Change and Change Influence
This activation of IPPM is to check the transmission quality between RNC and NODEB;
When active we will use the information of QOS so if the QOS configuration on the TX
is different with RNC&NODEB there will has alarms and we need try to fix it
together with transmission team.
1.4
License .
This operation not related to license.
1.5
Version information
Current Version:
RNC: V900R016C00SPC660
NODEB: V100R009C00SPC230
U2000: V200R014C00SPC220
The current version supports to implement these adjustments.
1.6
Impact on the System during the Adjustment

No affect for the service.
1.7
Equipment Running Check

Before operation, make sure no TX problems of this siteand all cells are normal.

Page 4 of 16
2 Preparations for Change

2.1
During 00:00 6th to 05:00 6th Apr., we need to ask customer stop any operation
with this RNC and sites.
2.2
Change Period
Node_B_M2000
Tracker
HID-9021_0630_Tulancingo_II
HID-9029_0633_GUADALUPE
HID-9033_0629_SAN_NICOLAS
HTGO8002
HID-9035_0634_Hinojosa
HID-9039_0763_Tulancingo_Centro
HTGO8010
HID-9069_0963_Santiago_Tulantepec
HID-9071_0698_Tepeyac
HID-9080_1685_Blvd_Bicentenario
HID-9083_1686_Tulancingo_Oriente
HID-9084_1687_Huapalcalco
HTGO8001
HID-9124_1946_Glorieta_Zapata
HTGO0001
HID-9121_1935_Tulancingo_Centro
HTGO0013
COW-0017-2_1529_COW_Tulancingo
MCR92-0006A_0099_CAE_Tulancingo
MCR92-
HID-9021
HID-9029
HID-9033
HID-9033
HID-9035
HID-9039
HID-9039
HID-9069
HID-9071
HID-9080
HID-9083
HID-9084
HID-9009
HTGO0001
HTGO0001
HTGO0013
HTGO0013
0054A_0364_Calle_Sinaloa_Tulancingo_I
MCR92-0012A_0141_Elektra_Tulancingo
HID-9009_0631_Tulancingo
2.3
Date
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
00:00~05:00 Apr 7
Composition of Change Team and Responsibility of Team Members
-Wireless Team Activity execution

-RF Team: Performance analysis
2.2.1
Change Team of Huawei Company
Name
Responsibility
Telephone No.
Page 5 of 16
Braulio
2.2.2
Huawei On-site Monitoring Team
Name
Luis Edwin
2.2.3
Responsibility
Wireless Department
RF Department
Telephone No.
5510070841
Huawei Support & Guarantee Team
Name
Xiongchanmou
2.4
5570470797
Wireless Department
Responsibility
GTAC Mexico
Telephone No.
5519628010
Support
Change Risks and Countermeasures

If the QOS has problems the activation may failed with alarms.
2.5
Check before Change

Perform preparation tasks at least three days before the adjustment.
1check the IPPATH ID of RNC
3
P
2check the IPPATH ID of NODEB;

3 : check the QOS of RNC and NODEB and confirm with TX team
rocedure
3.1
Operation Steps for Change
N Change Step
1
Get backup configuration

Data backup
1
2
Operation
from RNC. Use backup
Implementat
Time
ion Person
Braulio
11:00
Enrique
function on M2000.
RNC equipment running
status check

Open device Maintenance of

RNCcheck if the RNC
Braulio
11:25
Enrique
boards runs well or not .
Page 6 of 16
Open U2000run
ACT IPPM on
RNC&NODEB side
command
Braulio
12:00
Enrique
,and copy the script into

this. then run the
command.
Braulio
1:00
Enrique
Braulio
2:00
Active the backup CFG
Enrique
Braulio
before
Rollback (if change
File and connect the
Enrique
operation failure )
original RRU and
Check the alarms
Check the alarms
Check the IPPM KPI
Check the KPI of IPPM
4:30
antennas back.
3.2
Back up
Query Alarms
Obtain the current alarm list and save. In the Main Topology click right button
on the RNC, select Query Alarm/Event and then choose Alarm List.
Backup license;
RNC CFGMML and backup files
Use M2000 backup function to select related RNC and backup.

Page 7 of 16
And export the configuration, open target RNC LMT ,run command :EXP CFGMML; and
EXP CFGBCP; then collect the result like this:
Backup CFGBCP files

Page 8 of 16
Backup CFGMML files
Check operating status of boards

All boards should be working properly.

Page 9 of 16
3.3
Change Period
The change period is from 00:00 to 1:00.
3.4
Change step and operation
A. Open the LMT of related RNC:

Select the target RNC and click right button on mouse, then select the Maintenance Client,
you will open the LMT .
B. Run the ACT IPPM scripts on RNC

Page 10 of 16
ACT IPPM.txt
C. Run the ADD IPPMSESSION scripts on NODEB:
ADD
IPPMSESSION.txt

Page 11 of 16
4 Verifying the operation

4.1
Check the RNC MOCN script have already configured successfully.

Use the commands to check the configurations are all normal:
RNC side
Use commandDSP IPPM to check if the IPPM status is UP or not
NODEB side
Use command DSP IPPMSESSION to check the IPPM status is UP or not
4.2
Check Alarms after adjustment and ensure no related alarms to this activity.
4.3
Monitor KPIs
*If the verification results are normal, the operation is successful.
*If a fault occurs during the verification and cannot be rectified, perform the rollback.

Page 12 of 16
5 Rollback
5.1
Rollback Responsibility
Name
Braulio Enrique
5.2
Responsibility
Wireless Department
RF Department
Telephone No.
5570470797
Overall Description of rollback
Change back the MOCN Activation on RNC

5.3
Rollback Procedure
N Change Step
1
Get information for
This RNC
1
Operation
Get alarmlog and

operationlog and CHR
Time
ion Person
Braulio
4:30
Enrique
from RNC.
Open U2000run
command
Fallback IPPM
Implementat
Braulio
4:40
Enrique
,and copy the script into

this. then run the
Check the alarms
5.4
command.
Check the alarms about
IPPM
Braulio
5:00
Enrique
Definition of change failure

After the change, IPPM could not be active and no alarms about IPPM.
5.5
Information Collection Before rollback
Collect alarms, KPIs and activity logs and make some port trace to see where the error
originated and what can be done to avoid it.
5.6
Change back steps

Go to M2000 and in the MML command tab ,Run rollback script on target RNC.

Page 13 of 16
A. Open the LMT for related RNC:

Select the target RNC and click right button on mouse, then select the Maintenance Client,
you will open the LMT.
B. Fallback RNC IPPM:

DEA IPPM.txt
C. Fallback NODEB IPPM

RMV
IPPMSESSION.txt
5.7
5.7.1
Tests after Change back

After roll back, check whether the RNC and NODEB cells status are normal or not.
Use the commands to check the configuration are all normal:
RNC side
Use commandDSP IPPM to check if the IPPM status is UP or not
NODEB side

Page 14 of 16

Use command DSP IPPMSESSION to check the IPPM status is UP or not
5.7.2
Check if any new alarms come out.
5.7.3
Check the service on site for RNC users runs well
5.7.4
Monitor KPIs
5.8
Change back Risk analysis

There is no risk when we roll back because it was working well on the equipment before.

Page 15 of 16
6 Resources
M2000 ACCOUNTS

Page 16 of 16

20 Sites IPPM Active Apr6 To Apr7

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

20 Sites IPPM Active Apr6 To Apr7

Uploaded by

Copyright:

Available Formats

AT&T NETWORK

20 sites IPPM active

Implementation Solution for Change

Description of Change and Change Influence........................................................4

License should be apply before a week..................................................................6

Impact on the System During the Adjustment........................................................6

Equipment Running Check.....................................................................................6

Preparations for Change

with this two RNCs.....................................................................................................................7

Composition of Change Team and Responsibility of Team Members...................7

Change Team of Huawei Company..............................................................................7

Huawei On-site Monitoring Team................................................................................7

Huawei Support & Guarantee Team............................................................................7

Change Risks and Countermeasures.......................................................................8

Check Before Change.............................................................................................8

Operation Steps for Change..................................................................................11

Change step and operation....................................................................................15

Verifying the operation

Check the RNC MOCN script have already configured successfully..................17

Overall Description of rollback............................................................................19

Definition of change failure..................................................................................20

Technical support website:

Implementation Solution for Change

Information Collection Before rollback...............................................................20

Change back steps.................................................................................................20

Tests after Change back........................................................................................22

Check if any new alarms come out.......................................................................24

Check the service on site for RNC users runs well..............................................24

Change back Risk analysis...................................................................................24

Technical support website:

Implementation Solution for Change

Description of Change and Change Influence

Impact on the System during the Adjustment

Equipment Running Check

Technical support website:

Implementation Solution for Change

2 Preparations for Change

Composition of Change Team and Responsibility of Team Members

-Wireless Team Activity execution

Change Team of Huawei Company

Implementation Solution for Change

Huawei On-site Monitoring Team

Huawei Support & Guarantee Team

Change Risks and Countermeasures

Check before Change

2check the IPPATH ID of NODEB;

Operation Steps for Change

Get backup configuration

from RNC. Use backup

Technical support website:

Open device Maintenance of

boards runs well or not .

Implementation Solution for Change

,and copy the script into

Active the backup CFG

Rollback (if change

File and connect the

original RRU and

Check the alarms

Check the alarms

Check the IPPM KPI

Check the KPI of IPPM