2. Owd600306 Ggsn9811 Routine o&m Issue1.0

www.huawei.com

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

GGSN9811 Routine O&M

Page1Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Foreword

� This slide describes the contents and procedures of GGSN9811

routine maintenance, providing a reference for you to make an

office maintenance plan.


References

� Maintenance Manual-Routine Maintenance


Objectives

� Upon completion of this course, you will be able to:

� Describe the maintenance purpose

� Complete maintenance tasks

� Backup and restore data

� Replace boards of GGSN9811


Contents

1. Overview

2. System State Check

3. Data Backup and Restoration

4. Board replacement


Contents

1. Overview



4. Board Replacement


Maintenance Classification

� Classification on Method

� Normal maintenance

� Abnormal maintenance

� Classification on Period

� Burst maintenance

� Daily routine maintenance

� Period routine maintenance


Maintenance Tasks

� The maintenance of the GGSN9811 includes the

following tasks.

� Keep the equipment in good condition and ensure that the

system performance reach standards.

� Optimize the network to ensure the communications in the

service area in good quality.

� Remove communication faults rapidly and accurately to ensure

the communications.


Maintenance Tasks

� Performance management

� Including number of subscribers, number of PDP context

activations, traffic and CPU load.

� Network optimization

� System survey

� Data analyze

� Optimization planning and implementation


Contents

1. Overview





Version Management

� To see the version information of GGSN9811, login the

GGSN by LMT and use the LST VER command %%LST VER:;%%

RETCODE = 0 Execution succeeded

Result of current software query

--------------------------------

Current Software Version = GGSN9811V800R002ENGC02B025

Current Software Status = Normal

--- END


Version Management

� To the version information of the board, use the

LST BRDVER command %%DSP BRDVER:;%%


Board version

----------------------

Slot Type software version hardware version

1 LPU GGSN9811V800R002ENGC02 PCB2,BIOS003,009L

2 LPU GGSN9811V800R002ENGC02 PCB2,BIOS003,009L

3 SPU GGSN9811V800R002ENGC02 PCB2,BIOS003,009L

4 SPU GGSN9811V800R002ENGC02 PCBA,BIOS002,003L

9 SRU GGSN9811V800R002ENGC02 PCB0,BIOS003,005L

10 SRU GGSN9811V800R002ENGC02 PCB0,BIOS003,005L

(Number of Results = 6)


License Management

� To see the license file information, use the LST LICENSE

command%%LST LICENSE:;%%


Actived License file AreaId = 0

License file area list:

Valid file area ID = 0, File len = 2187 ,File name = ggsn.dat


License Management

� To see the detailed information of license, use the

DSP LICENSE command%%DSP LICENSE:;%%


License Info

------------

License type = NORMAL

License deadline = year 2007 month 7 day 1

PDP Context Numbers of Supporting GGSN Basic Function = 1050000

PDP Context Numbers of Supporting HandOver and Roaming Between 2.5/3G = 1050000

PDP Context Numbers of Supporting Radius Non-realtime Charging = 1050000

PDP Context Numbers of Supporting Radius Realtime Charging = 1050000

..........................................


Log Management

� Querying the Operation Log Information

� Use LST LOG command%%LST LOG:;%%


Query operation log

-------------------No. = 1

Date = 2007-01-10Time = 15:36:01

User ID = 1

User name = admin

Terminal IP address = 10.77.204.226

Operation Result = Execution succeeded

Return code = 0

Command = ACT INTF: INTFN="ethernet1/0/7";


Log Management

� Dumping the log file

� The dump function of log file can backup the log files though

manual dump or automatic dump.

� Step 1 - Specify an FTP server using SET FTPSVR command

SET FTPSVR: SVRN="10.77.72.106", USRN="dump", PWD="dump";

� Step 2 - Dump the files using BCK GRPFILE command

BCK GRPFILE: FN="*.olg";

1. wildcard "*" can be used to represent multiple files

2. The suffix can only be ".alm", ".prf", ".olg" or ".tmf"


CPU Management

� Method⒈ - Use the DSP BRDCPU command%%DSP BRDCPU:;%%


Display board CPU usage

-----------------------

Slot Type CPU usage(%)

1 LPU 4

2 LPU 4

3 SPU 1

4 SPU 1

9 SRU 11

(Number of results = 5)


CPU Management

� Method ⒉ - In the “Maintenance Navigator” window of the

O&M System, select [Common Monitoring/CPU usage] to

start the task to monitor CPU utilization.


CPU Management

� Method ⒉ - Then set slot number in the parameter settings

window to start the CPU occupation monitoring.


Contents

1. Overview





Data Backup� Information about Backup

� Files Needing Backup

� The GGSN9811 data can be stored on the hard disk or Flash of the SRU. The system periodically synchronizes the data to the active/standby SRUs; so you only need to back up the data to the activeactive SRUSRU when performing manual backup. The data to be backed up are as follows:

� Two configurationconfiguration files: flash:/vrpcfg.zip and hd:/bam/mml.txt;

�� AlarmAlarm datadata file: The file is stored in the directory of hd:/bam/data/alm and its extension name is alm;

�� PerformancePerformance datadata file: The file is stored in the directory of hd:/bam/data/mrf and its extension name is prf;

�� TraceTrace datadata file: The file is stored in the directory of hd:/bam/data/trc and its extension name is trc;

�� OperationOperation loglog file: The file is stored in the directory of hd:/bam/data/olg and its extension name is olg.


Data Backup

� Information Backup

� Server Information to be Backed Up

� For example, the FTP Server information to be backed up is as

follows:

– The IP address is 10.10.10.1;

– The FTP username is “ggsn”;

– The password is “ggsn”.

– In practice, you need to back up the server information as required.

� Automatic Backup

� SET FTPSVR


Data Backup

� Manual Backup

� Backing Up the Configuration Data Files

� SAV CFG;

– (Save the configuration data in the memory to the file and synchronize

the data to the active/standby SRUs.)

� ULD GENFILE: SRCF="flash:/vrpcfg.zip", DSTF="vrpcfg.zip", IP="10.10.10.1", USR="ggsn",pwd=”ggsn”;

– (Back up the vrpcfg.zip file to the FTP server 10.10.10.1 using the

username and password “ggsn”.)

� ULD GENFILE: SRCF="hd:/bam/mml.txt", DSTF="mml.txt", IP="10.10.10.1", USR="ggsn",pwd=”ggsn”;

– (Back up the mml.txt file to the FTP server 10.10.10.1 using the

username and password “ggsn”.)


Data Backup

� Manual Backup

� Backing Up the Alarm Data File

� SWP DIR : DIRNAME=”hd:/bam/data/alm”;

– (Set the current path of the GGSN9811 as the directory of the alarm file “hd:/bam/data/alm”.)

� LST GENFILE: DIR="*.alm";

– (Query all of the alarm data files in the alarm directory.)

� ULD GENFILE: SRCF="xxx.alm", DSTF="xxx.alm", IP="10.10.10.1", USR="ggsn",pwd=”ggsn”;

– (Back up the alarm file [such as alarm.alm] to the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Backup

� Manual Backup

� Backing Up the Performance Data File

� SWP DIR : DIRNAME=”hd:/bam/data/prf”;

– (Set the current path of the GGSN9811 as the directory of the performance data file “hd:/bam/data/prf”.)

� LST GENFILE: FN="*.mrf";

– (Query all of the performance measure data files in the performance measure directory.)

� ULD GENFILE: SRCF="xxx.mrf", DSTF="xxx.mrf", IP="10.10.10.1", USR="ggsn",pwd=”ggsn”;

– (Back up the performance measure file [such as performance.mrf] to the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Backup

� Manual Backup

� Backing Up the Trace Data File

� SWP DIR : DIRNAME=”hd:/bam/data/trc”;

– (Set the current path of the GGSN9811 as the directory of the trace data file “hd:/bam/data/trc”.)

� LST GENFILE: DIR="*.trc";

– (Query all of the trace data files in the trace directory.)

� ULD GENFILE: SRCF="xxx.trc", DSTF="xxx.trc", IP="10.10.10.1", USR="ggsn",pwd=”ggsn”;

– (Back up the trace file [such as trace.trc] to the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Backup

� Manual Backup

� Backing Up the Operation Log File

� SWP DIR : DIRNAME=”hd:/bam/data/olg”;

– (Set the current path of the GGSN9811 as the directory of the operation log file “hd:/bam/data/olg”.)

� LST GENFILE: DIR="*.olg";

– (Query all of the operation log files in the operation log directory.)

� ULD GENFILE: SRCF="xxx.olg", DSTF="xxx.olg", IP="10.10.10.1", USR="ggsn",pwd=”ggsn”;

– (Back up the operation log file [such as operationlog.olg] to the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Restoration

� Before restoring the data, you need to consider the following situations:

� The FTP server has been started.

� The data is stored in the working directory of the FTP server (or you can divide the working directory of the FTP server into multiple sub-directories for storing different files).

� Each file is stored in a standard file name.

� Generally, the configuration data shall be restored first.


Data Restoration

� Restoring the Configuration Data

� SWP DIR: DIRNAME="flash:/";

� (Set the current working directory of the GGSN9811 as “flash:/”.)

� DLD GENFILE SRCF="vrpcfg.zip", IP="10.10.10.1", USR="ggsn", PWD="ggsn";

� Or,

� DLD CFGFILE: IP="10.10.10.1", USR="ggsn", PWD="*****", DIR="flash", FT=ALLFILE, FN="vrpcfg.zip";

� (Restore the vrpcfg.zip file to the Flash of the SRU from the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Restoration

� Restoring the Alarm Data File

� SWP DIR: DIRNAME="hd:/bam/data/alm";

� (Set the current working directory of the GGSN9811 as “hd:/bam/data/alm”.)

� DLD GENFILE SRCF="xxx.alm", IP="10.10.10.1", USR="ggsn", PWD="ggsn";

� (Restore the alarm file [such as alarm.alm] from the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Restoration

� Restoring the Performance Data File

� SWP DIR: DIRNAME="hd:/bam/data/prf";

� (Set the current working directory of the GGSN9811 as “hd:/bam/data/prf”.)

� DLD GENFILE SRCF="xxx.mrf", IP="10.10.10.1", USR="ggsn", PWD="ggsn";

� (Restore the performance measure file [such as performance.prf] from the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Restoration

� Restoring the Trace Data File

� SWP DIR: DIRNAME="hd:/bam/data/trc";

� (Set the current working directory of the GGSN9811 as “hd:/bam/data/trc”.)

� DLD GENFILE SRCF="xxx.trc", IP="10.10.10.1", USR="ggsn", PWD="ggsn";

� (Restore the trace file [such as trace.trc] from the FTP server 10.10.10.1 using the username and password “ggsn”.)


Data Restoration

� Restoring the Operation Log File

� SWP DIR: DIRNAME="hd:/bam/data/olg";

� (Set the current working directory of the GGSN9811 as “hd:/bam/data/olg”.)

� DLD GENFILE SRCF="xxx.olg", IP="10.10.10.1", USR="ggsn", PWD="ggsn";

� (Restore the operation log file [such as operationlog.olg] from the FTP server 10.10.10.1 using the username and password “ggsn”.)


Contents

1. Overview





Board Replacement

� Preparation

� Confirm Board Position and Type before Replacing Boards

� Board work in Active/Standby mode: SRU/SPU

� Board work in other mode: LPU

� Check the software version and BAM version of the new board


Board Replacement

� Preprocess the Board in Active/standby Mode

� Use the command LST BRD in the LMT to query the

active/standby status of the SRU/SPU boards.

� If the board is in slave mode, replace this board directly.

� If the board is in master mode, perform the following operations:

� Step 1: use the commands ACT SRUSWP or ACT SPUSWP to

enable the SRU/SPU switch.

� Step 2: use the commands SWP SRU or SWP SPUBD to switch

the board from master mode to slave mode, so as to ensure that

the board to be removed is in slave mode.


Board Replacement

� Procedure

� Wear an Antistatic Wrist Strap

� Remove Cables (Optional)

� Remove the Old Board

� Insert the New Board

� Install Cables (Optional)


Board Replacement

� Check

� Common check

� Observe the status of the board indicators

� Query the status of the board (LST BRD)

� Synchronize SRU License

� Use the command ULD LICENSE to upload a License file from the

master SRU to the FTP Server for backup.

� Use the command DLD LICENSE to download a License file from

the FTP Server to the hard disk of the slave SRU, and update the

License information of the slave SRU.


Board Replacement

� Check

� Special check

� Besides, perform the following operations for such boards working

in active/standby mode as SPU/SRU

� Perform a forced active/standby switchover using the commands

SWP SPUBD or SWP SRU to check whether the board can work

normally.


Summary

� Maintenance can be divided into different categories

� You can use command or GUI for maintenance of

GGSN9811

� Command used for data Backup and Restoration

� Commands for boards replacement

Thank youwww.huawei.com

Documents

2. Owd600306 Ggsn9811 Routine o&m Issue1.0