Network Change MOP

Change
Maintenance Operation Procedure
[RMV E1 INTERFACE BOARD ON
THE RNC]

1 05 February 2018
Network Change MOP

1. High Level Change Overview

1.1. [to solve the Traffic Exceed Capability Alarm]:

1.1.1. DPU]

2. Change Objectives
2.1. [BSC ]

2.2. Existing Network Layout (Optional)

2.3. Future Network Layout (Optional)

2.4. Monitoring (Optional)

2.4.1. [Contact the NOC and let them know this change is being done and all
monitoring to these devices should be disabled]
2.4.2. [Date monitoring will be (or was) implemented]
2.4.2.1. N/A
3. Pre-Validation Change Tasks (Baseline)
3.1. [CI 1]
1. query Site status
2. query current alarm
3. backup cfgbcp file
4. backup NE

4. Change Execution Steps (Implementation)

4.1. [CI 1]

4.1.1. Implementation
1. RMV the boad on the BSC
2. check the software
3. RUN script

4.1.2. Post-Validation
1. confirm alarm has clear
2.

5. Implementation Post-Validation Change Tasks (Post-Change)

2 05 February 2018
Network Change MOP

5.1. Contact the NOC and let them know this change is being verified.
5.2. Repeat all tasks listed in step 3 of this plan. Save this output and compare to the saved
output of the pre-validation tasks. If there are discrepancies, they need to be resolved
or the change needs to be backed out.
5.3. If Validations are successful
5.3.1. Contact the NOC and let them know this change is complete.
5.3.2. Get the status of all existing alarms and ensure none are the result of any
configuration items in this implementation.
5.3.3. Create an update in CMS detailing this change. Attach the pre- and post-
verification results and change log to the update.
5.4. If validation tasks are not successful
5.4.1. Continue with Back Out Change Tasks below.
6. Back Out Change Tasks
6.1. Contact the NOC and let them know this change is being backed out.
6.2. [CI 1]
6.2.1. Rollback Implementation
1. rmv board
2. load rollback script
3.

6.2.2. Rollback Post-Validation

1.
2.
3.
4.

6.3. [CI 2]
6.3.1. Rollback Implementation
1.
2.
3.
4.

6.3.2. Rollback Post-Validation

1.
2.
3.
4.
6.4.
7. Back Out Post-Validation Change Tasks
7.1. Contact the NOC and let them know this change is being verified
7.2. Repeat all tasks listed in step 3 of this plan. Save this output and compare to the saved
output of the pre-validation tasks in step 3.

3 05 February 2018
Network Change MOP

7.3. Contact the NOC and let them know this change is successfully reverted.
7.4. Create an update in CMS detailing the reasons this change was backed-out. Attach the
pre- and post-verification results and change log to the update.

4 05 February 2018