VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.

0 C2 Vodafone Restricted Page | 0

VODAFONE INDIA LIMITED

Removing Insufficient Space on CC Board

Method of Procedure (MoP) v1.0

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 0

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 1

Document Details :
Domain
Document No. Document Title Author
Owner

VIL/SNOC/MOP/20179/ Removing SNOC CHM ZTE BSS- Removing Swajeet

Sumit Nangia
Insufficient Space on CC Board Insufficient Space on CC Board Shukla

Reviewers:
Reviewed
Name Version Approved Position
Date

Nilesh Amte, Suraj Sinha SNOC-Change Management Head

Sumit Nangia 1.0 Lead - Mobility

Abhijit Ray RAN Lead

Approvers:
Name Version Approved Position Approval Date

Vinay Tyagi 1.0 SNOC Head

Distribution List:
Name/Position / Available at Published Date
SNOC, Circle BSS team, Corporate team

Next Review*:
Next Review Date Domain Owner
Sumit Nangia

*Document should be reviewed once every quarter or whenever there is a major change, whichever is
earlier. For Feedback/Suggestions please drop a mail to: [email protected]

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 1

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 2

Contents

1. Purpose of Document.....................................................................................................................3

2. Objective.........................................................................................................................................3

3. Scope...............................................................................................................................................3

4. Resources........................................................................................................................................4

5. Impact on Service...........................................................................................................................4

6. Detailed Step by Step Procedures.................................................................................................4

7. Activity Process and Time Line..................................................................................................10

8. Post Execution Checks.................................................................................................................10

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 2

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 3

1. Purpose of Document
 This technical document covers the activity of Removing Insufficient Space on CC Board in the
OMMB for Circles. The purpose of this document is to Create Space in CC Board to perform
following Activity like Version Upgrade, New Software Addition, New Patch Activation, New
technology Addition on site etc.

2. Objective
 The objective of this MOP is to provide the user as to how to perform Removing Insufficient
Space on CC Board in OMMB.

3. Scope
 The scope of this process document is to present the process Removing Insufficient Space on CC
Board in OMMB, which is to be observed by SNOC, for ZTE based circles and Corporate Team.
 This process is for Vodafone Managed Circles Only.

4. Resources

 NETNUMEN Applications via SRAS.

 BSS Engineer should be technically equipped for OMMB activity.
 SPOC’s details ( Circle & SNOC)

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 3

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 4

5. Impact on Service
 Outage Involved: YES
 Outage Severity: Major
 Outage Severity in case of fallback: Total
 Outage Time & Duration: 20 mins

6. Detailed Step by Step Procedures

1. Symptom
The problem of insufficient flash space on the CC board of a base station often occurs in network
maintenance or base station upgrade. Consequently, data may not be writeable or new version files
may not be storable on the CC board. To solve this problem, flash space on the CC board should
be freed-up effectively.

2. Probable cause
This problem is caused because the space usage on the CC board reaches the configured threshold
or because there is not enough free space on the CC board to store new version files.

3 .Action

(1) Clean up the flash space on the OMC.

Enter the SDR Dynamic Data Management page of the OMCB, and perform the operations as shown in
Figure 1. Log files are cleaned up in these operations. Detailed information about them can be found in
base station upgrade guides. The UI may vary with the product model, but you can basically perform
the operations as follows: Enter the SDR Dynamic Data Management page, select Device Group
Object, select Clean Disk on the Device Group Object tab, choose the log files to be cleaned up, and
click OK.

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 4

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 5

Figure 1 Flash Space Cleanup

(2) Delete backup version files

If log file cleanup still cannot clear related alarms or provide enough space for new version files, you
can check whether there are backup version files stored on the CC board, and delete them if any.
You can delete the backup version files as follows: Multiple Mode Station Software
Management>Station Version Management>Software Version Info>Version Info Query>Delete
Version, as shown in Figure 2.

Figure 2 Backup Version File Deletion

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 5

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 6

(3) Log in to the CC board and delete the version files.

In the case that version files cannot be deleted on the OMCB, you can log in to the CC board and delete
some of them. Figure 3 shows the telnet window after a successful login.
Figure 3 Telnet Window after a Successful Login to the CC Board

Figure 3 Telnet Window after a Successful Login to the CC Board

Figure 4 shows the directory of the version files and its space usage information.

Figure 4 Directory of the Version Files and Its Space Usage

Run the following commands to enter the directory and delete the version files in this directory:
#cd /mnt/flash/PRODUCT/UMTS/SW1
# rm file name
Keep deleting the files until there is enough flash space, which is calculated automatically.
After the backup version files are deleted, the alarm for insufficient flash space is cleared, but the alarm
for abnormal backup version files is raised. You can clear the alarm by deleting the backup version
files on the OMCB.

(4) Reconfigure the CC board

1) Check the status of the ping packet

If the problem cannot be solved using all the above methods, the CC board is faulty, and should be
replaced or reconfigured.

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 6

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 7

Open two cmd windows. Enter "telnet 192.254.1.16" in one window, and do not press the Enter button.
Run the "ping 192.254.1.16 –t" command in the other window, and check the status of the ping packet,
as shown in Figure 5. 192.254.1.16 is the default IP address of the CC board.

Figure 5 ping Packet Status

If the CC board can be pinged, press Enter in the first cmd window, and telnet to the CC board with the
username and password "zte" and "zte" respectively.

2) Telnet to the CC board.

If the telnet UI shown in Figure 6 is displayed after a successful login, enter bs and press Enter
terminate the launch process

Figure 6 telnet UI 1 after a Successful Login

If the telnet UI shown in Figure 7 is displayed after a successful login, run the following commands:

Figure 7 telnet UI 2 after a Successful Login

# cd /GSM/SW1/data/temp/

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 7

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 8

# rm -rf *
The CC board automatically restarts. After that, repeat step a.

3) Format the CC board.

After the launch process terminates, run the following commands:

protect off all
tffs_uinit
tffs_format
The CC board starts being formatted, which takes about 30 minutes.

4) Upload the initialization version files (using V4.11.10.14P06 as an example).

Extract the attached file to D:\cc.

Open a new cmd window, and run the following commands:
ftp 129.254.1.16 //Connect to the CC board via ftp.
zte/zte – Enter the username and password.
mkdir BIN – Create a BIN directory.
cd BIN – Enter the BIN directory.
hash – Open the transport process.
bin – Set the transport format to binary.
put D:\cc\ DefaultCpu.bin – Upload the CPU version files to the CC board.
put D:\cc\ DefaultFpga.bin – Upload the FPGA version files to the CC board.
Figure 8 and Figure 9 show the command execution process and result.

Figure 8 Command Execution Process

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 8

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 9

Figure 9 Command Execution Result

Power off the CC board, and restart it.

Load the configuration files using LMT, and log in to the CC board.
Upload the official version files
Enter the version management window, and upload the official software version files. Activate the
official version, restart the CC board, and delete the version files for field use.
This step uses the V4.11.10.14P06 software packet as an example:
CPU and FPGA version:
Unzip the file and put it in Disc D:
D:\cc\ DefaultCpu.bin
D:\cc\ DefaultFpga.bin
Verification
Restart the CC board, and check whether login and commissioning operations can be performed
properly using LMT.

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 9

 VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 10

7. Activity Process and Time Line

Sr
Execution Outage Time Duration for Activity in
No Activity Process
Time Inv mins
.
Checking CR if all required data
1 Day No 20
provided
2 Validate the plan Day No 10
Removing Insufficient Space on CC
3 Night yes 10 per site
Board
5 Post check Night Yes 10

8. Post execution checks

Removing Insufficient Space on CC Board

S. Statu Remark
Points need to be checked
No. s s
         
1 Check Flash Space on CC Board      
         
2 Cross check all cell services      
         
3 Ensure after activity no alarm in network      
         

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 10

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 11

VIL/SNOC/MOP/2019/Insufficient Space on CC Board _ ZTE_v1.0 C2 Vodafone Restricted Page | 11