Sie sind auf Seite 1von 38

New Service Request

Country
Customer Company Name
Customer Name
Customer Information Customer Mobile Number
Customer Email Address
Customer Fixed Number
Location/City
Ticket Type
Priority
Category
Product

Summary(240)

Affected Equipment Quantity


Ticket Information
Software Version

Details(5000)

additional comments related to Problem


RTTS ( Customer Ticket Reference No)
ew Service Request

Malawi
Telecom Network Malawi
Telecom Network Malawi
265881244624
fanizo.jere@tnm.co.mw

BT-RNC
Customer Support
Major
Wireless-GSM BSS

paging congestion on the abis

some sites in the BSC


V900R018ENGC10ENGC10SPC570

some 2G sites are expriencing paging congestion on the abis

54200583927
Product Class Product Requested Info.
Detailed problem description
Version and installed patches
call scenario and network structure
MSOFTX 3000 User trace with internal module and user log
Performance measurement tasks ( *.csv)
Alarm Log ( *.csv)
Device alarm
Informaiton collected by the InfoCollector tool
Detailed problem description
Core CS
Version and installed patches
DSP CFG
UMG 8900
Alarm Log ( *.csv)
Run LOG, Operation LOG and Running LOG
Informaiton collected by the InfoCollector tool
Detailed problem description
iGWB traces
IGWB
original and final CDRs
Format and ini files
Version and installed patches
Workshop database
the details of service with problems and the network diagram
of the service
SOFTX 3000 User trace with inter module and user log,calling network
structure, and related protocols used, SIP for example.
Performance measurement tasks ( *.csv)
Alarm Log ( *.csv)
Device alarm and device log
Version and installed patches
DSP CFG
Core NGN UMG 8900
Alarm Log ( *.csv)
Run LOG, Operation LOG and Running LOG
iGWB traces
IGWB other
Core NGN

IGWB
original and final CDRs
Format and ini files
Snapshot from SySmonitor
N2000
make synchronization for the network elements
C&C08 like SX3000
SGSN configuration file (mml file)
SGSN System log file (SLG file)
SGSN Alarm log file (HLM file)
SGSN V8 product
SGSN System log file (OLG file)
Performance measurement file
Trace file

SGSN configuration file (mml file)

SGSN V9 product
SGSN Alarm log file (csv file)

Performance measurement file


Trace file

Core PS SGSN configuration file (mml file)

USN product
SGSN Alarm log file
Performance measurement file
Trace file
GGSN configuration file (mml file)
GGSN log file (log file)
GGSN V8 product GGSN Alarm log file (HLM file)
Performance measurement file
Trace file
GGSN configuration file (mml file)

GGSN V9 product
GGSN log file (log file)
GGSN Alarm log file (HLM file)
GGSN V9 product

Performance measurement file

Trace file
CG configuration file.
CG product CG log file
Trace file
WASN configuration file
WASN Alarm file
WASN V2 product WASN operation log
WASN log file
Performance measurement file
WASN configuration file
WASN Alarm file
WASN V3 product
WASN log file
Performance measurement file
DNS product DNS log file
Version +patch
performance task (*.csv)
OMCAutostar report
M2000 product Alarm log
Traces file
explorer logs
Core Integration
print screen of the error messages
(HLR/M2000)
Version +patch
performance task (*.csv)
configuration related to the problem
HLR9820 product
Alarm log
Traces
autocheck report
Version and installed patches
Workshop database
CSOFTX 3000

Core CDMA
User trace with inter module and user log
CSOFTX 3000
Performance measurement tasks ( *.csv)
Alarm Log ( *.csv)
Device alarm
Core CDMA Version and installed patches
DSP CFG
UMG 8900 C
Alarm Log ( *.csv)
Run LOG, Operation LOG and Running LOG
iGWB traces
IGWB original and final CDRs
Format and ini files
Related to
Basic Information
Basic Information
Problems related to Service flow
Problems related to Service flow
Problems Related to Performance
Problems related to Hardware
Problems related to Hardware
Basic informaiton
Basic informaiton
Basic Information
Data configuration Problems
Problems related to Hardware
Problems related to Hardware
Basic informaiton
Basic informaiton
Problem related to Billing Center service
Problem related to Billing Center service
Problem related to Billing Center service
Basic Information
Data configuration Problems

Problems related to Service flow


Problems Related to Performance
Problems related to Hardware
Problems related to Hardware
Basic Information
Data configuration Problems
Problems related to Hardware
Problems related to Hardware

Problem related to Billing Center service


Problem related to Billing Center service
Problem related to Billing Center service
Problem related to Billing Center service
Problem related to Alarms
Problem related to SYNC

Basic Information
Problems related to Hardware
Problems related to Hardware
Problems related to Hardware
Problems related to Hardware+Problems rela
Problems related to Service flow

Basic Information

Problems related to Hardware


Problems related to Hardware+Problems rela
Problems related to Service flow

Basic Information

Problems related to Hardware


Problems related to Hardware+Problems rela
Problems related to Service flow
Basic Information
Problems related to Hardware
Problems related to Hardware
Problems related to Hardware+Problems rela
Problems related to Service flow

Basic Information
Problems related to Hardware

Problems related to Hardware

Problems related to Hardware+Problems rela


Problems related to Service flow
Problem related to Billing Center service
Problem related to Billing Center service
Problem related to Billing Center service
Basic Information
Problems related to Hardware
Problems related to Hardware
Problems related to Hardware
Problems related to Hardware+Problems rela
Basic Information
Problems related to Hardware
Problems related to Hardware
Problems related to Hardware+Problems rela
Basic Information+Data configuration Problems+Problems related to Hardware
Basic Information
Problems Related to Performance
Abnormal behaviour for OS,SYBASE or M200
Problems related to Hardware
Follow guide in case of request
problems related to OS
Basic Information
Basic Information
Problems Related to Performance
Data configuration Problems
Problems related to Hardware
Problems related to Service flow
abnormal behaviour for OS or Oracle
Basic Information
Data configuration Problems
Problems related to Service flow
Problems Related to Performance
Problems related to Hardware
Problems related to Hardware
Basic Information
Data configuration Problems
Problems related to Hardware
Problems related to Hardware
Problem related to Billing Center service
Problem related to Billing Center service
Problem related to Billing Center service
location
Try to give a detailed description about the problem
LMT
Description clear the call heppened under which scenario and the network structure
LMT
peroformance client or M2000
LMT
D:\MSOFTX3000\RUNLOG\FAM\
MSOFTX3000 InfoCollector for CPCI, VTS for ATCA
Try to give a detailed description about the problem
LMT
LMT
LMT
LMT
UMG8900Toolkits
Try to give a detailed description about the problem
use getiGWBinfo.exe tool (for ATCA please get this tool from the basic version folder)
iGWB client
C:\igwb\config\ini
LMT
LMT

trace from LMT


paeformace tasks as saved
LMT
E:\MSSQL\Data\;
LMT
LMT
LMT
LMT
C:\IGWB\trace

others
D:\frontsave\X3KF, E:\backsave\second\X3KF
C:\IGWB\config
from SYSmonitor client
synch from topo. View

/hda0/SGSN/CONFIG/
/hda0/bam/data/slg
/hda0/bam/data/hlm
/hda0/bam/data/olg
/hda0/bam/data/prf

Method I: Use the information collection tool provided by LMT and choose the corresponding files;
Method II: Execute the command of EXP MMLEX in the SGSN interface, invoke the tool of "Maintenance->File Transfer Service, choose
export file, download the configuration file in the /mit/mml directory.
It need operation level account at least.
Step 1 Log in to the LMT,execute EXP ALMDATA: FNAME="export file name"; in CGP command window.
Step 2 Use the file transfer service to obtain alarm log which is export file name.xml from /fm/alarminstance/manualexport/alarm in Export
file.
Step 3 Parse the alarm log by insight log tool in ps toolkits, then save as*.csv format.
Method I: Connect SGSN through WEBUI; export performance statistic result within specific time period; connect SGSN by LMT; invoke the tool of "Maintenance->Fil

Method I: Use the information collection tool provided by LMT and choose the corresponding files;
Method II: Execute the command of EXP MMLEX in the USN interface, invoke the tool of "Maintenance->File Transfer Service, choose
export file, download the configuration file in the /mit/mml directory.
Method I: Use the information collection tool provided by LMT and choose the corresponding files;
Method II: Log in the LMT and choose Alarm >query alarm log, save the result.
Method I: Connect SGSN through WEBUI; export performance statistic result within specific time period; connect SGSN by LMT; invoke the tool of "Maintenance->Fil

hd:/bam
hd:/logfile
hd:/bam/data/alm
hd:/bam/data/prf

V9R7C1:Connect GGSN by FTP; the configuration files are saved under the hd1:/vrpcfg.cfg;
V9R7C2:Connect GGSN by FTP; the configuration files are saved under the hd1:/soft/a/bam/cfg/vrpcfg.cfg
hd1:/log/*.log and hd1:/log/*.log.bz2
V9R7C1: Connect GGSN by FTP; the Alarm files are saved under the hd1:/bam/data/alm/alarm.alm;
V9R7C2: Connect GGSN by FTP; the Alarm files are saved under the hd1:/soft/data/alm/alarm.alm
V9R7C1: Connect GGSN by FTP; the Performance files are saved under the hd1:/bam/data/prf/*/*.mrf.bz2 and hd1:/bam/data/prf-
sp/*/*.mrf.bz2;
V9R7C2: Connect GGSN by FTP; the Performance files are saved under the hd1:/soft/data/prf/*/*.mrf.bz2 and hd1:/soft/data/prf-
sp/*/*.mrf.bz2;

UNIX CG: /opt/igwb/config/ini/igwb.ini, /etc/hosts, /etc/hostname.*, Windows CG: \"installed directory"\config\ini folder;
UNIX CG: /var/other/log , Windows CG: \installed directory\log
UNIX CG: /opt/igwb/trace, Windows CG: \installed directory\trace
hd:/bam
hd:/bam/data/alm
hd:/bam/data/olg
hd:/logfile
hd:/bam/data/prf
hd1:/soft/a/bam/cfg/vrpcfg.cfg
hd1:/soft/data/alm folder
hd1:/log folder
hd1:/soft/data/prf folder
ration Problems+Problems related to Hardware
#displayVersion
feedback performance sheet from both NE & M2000, use trace collection tool and feedback related traces
RUN the OMCAutoStar tool and follow the displayed instructions
Alarm list and run the OMCAutoStar tool
use trace collection tool (follow the displayed instructions when running the tool) and feedback related traces

print screen button


LMT
query the performance results from the performance client in *.csv format
use LST commands using MML GUI in LMT (V9R6 use command EXP MML)
LMT (LST ALMCFG) /var/log/message
LMT
RUN the autocheck tool and follow the displayed instructions
LMT
use manix tool and follow the displayed instructions
LMT
peroformance client
LMT
D:\CSOFTX3000\RUNLOG\FAM\
LMT
LMT
LMT
LMT
use getiGWBinfo.exe tool
iGWB client
use getiGWBinfo.exe tool
the tool of "Maintenance->File Transfer Service"; download XML formated XLS files from "Export/pm/perf_result"

the tool of "Maintenance->File Transfer Service"; download XML formated XLS files from "Export/pm/perf_result"
Product Class Product

N2000 ( DMS )

DataComm Routers,Switches,Firewalls

U2000

WDM/NG-SDH/SDH  products

Optical
Optical

Microwave product

U2000 / T2000

Broadband

Narrowband

Access
BMS N2000

U2000
Requested Info.
DMS detailed version
Enviroment of DMS
License information
No. of managed NE's
Alarm information
Snapshot of sysmonitor
Snapshot of error message
The detail topology(The most important)

Problem Description

VRP version
diagnose information
Log file & DBLG file
U2000 detailed version
Enviroment of U2000
License information
No. of managed NE's
Alarm picture
Snapshot of sysmonitor
Snapshot of error message
Detailed problem description and problem happened
time needed,what did you do before problem
happened?
How it is recovered?
NMS current alarms and history alarms, need to
include alarms parameters
and the time when problem happened.

if services are down, feedback the detailed down


services path informaiton:
which NE?which board?which port?which timeslot?

Collect related NE data using datacollector.


if configured SNCP or MSP protection group, feedback
Detailed problem description and problem happened
time needed,what did you do before problem
happened?
How it is recovered?
NMS current alarms and history alarms, need to
include alarms parameters
and the time when problem happened.
if configured SNCP or MSP protection group, feedback
abnormal event logs on NMS.
Collect related NE data using datacollector.

if services are down, 3G or 2G down?feedback the


detailed down services path informaiton:
which site?which board?which port?which timeslot?
(including the path from down sites to RNC).
U2000/T2000 detailed version
Enviroment of U2000/T2000
License information
No. of managed NE's
Alarm picture
Snapshot of sysmonitor
Snapshot of error message
NE version
Borads and type
Patches installed
Alarm history and statistics
Log files
NE version
Borads and type
Patches installed
Alarm history and statistics
Log files
DMS detailed version
License information
Enviroment of DMS
No. of managed NE's
Aarm information
Snapshot of error message
Snapshot of sysmonitor
U2000 detailed version
Enviroment of U2000
License information
No. of managed NE's
Alarm picture
Snapshot of sysmonitor
Snapshot of error message
How to get
HELP --> About --> Copy the version
HA or Single , Windows or Solaris
HELP --> License Management --> press CTRL+V
HELP --> License Management--> press CTRL+V
The full screenshot of the alarm detail information
Sysmonitor screen
Error message screen
Draw manually
(includeing interface number and ip addr)
1.Describe the abnormal phenomenon according with the
detail topology
2.problem happened time
3.what did you do before problem happened?
4.How it is recovered?
display version OR vrbd
dipslay diag OR cfcard:/
1.save logfile
2. cfcard:/log/
HELP --> About --> Copy the version
HA or Single , Windows or Solaris
HELP --> Lincense Management --> License Information
HELP --> Lincense Management --> License Information
The full screenshot of the alarm detail information
Sysmonitor screen
Error message screen

U2000>faulty>Browse history Alarms/Browse current Alarms

U2000>service>SDH trail/WDM trail>filter the target trail


right click the NE from the topo>collect NE data>login NE and
select full collect mode including the blackbox data
U2000>faulty>browse event logs

U2000>faulty>Browse history Alarms/Browse current Alarms

U2000>faulty>browse event logs


right click the NE from the topo>collect NE data>login NE and
select full collect mode including the blackbox data

HELP --> About --> Copy the version


HA or Single , Windows or Solaris
HELP --> Lincense Management --> License Information
HELP --> Lincense Management --> License Information
The full screenshot of the alarm detail information
Sysmonitor screen
Error message screen
l display version
display board
display patch
display alarm history
display log
l display version
display board
display patch
display alarm history
display log
HELP --> About --> Copy the version
HELP --> License Management --> press CTRL+V
HA or Single , Windows or Solaris
HELP --> License Management --> press CTRL+V
The full screenshot of the alarm detail information
Error message screen
Sysmonitor screen
HELP --> About --> Copy the version
HA or Single , Windows or Solaris
HELP --> Lincense Management --> License Information
HELP --> Lincense Management --> License Information
The full screenshot of the alarm detail information
Sysmonitor screen
Error message screen
Product Class

IN

DS

OSS

DE

OCS/CBS
Requested Info.

Use the collect data script in order to collect all the server
information; and send its output
(Ex.: collect.sun.83a4182b.SMCP01.2008.03.31.rar)

Traces
Configuration
Logs

Charge Issue:
1.Subscribe/unsubscribe logs:OpenDelete.log
2.JBOSS logs:server.log
3.Service logs:Common.log

If the register way is MML interface, Please feedback


uniportalcomm logs too.
MML,SMS issues:
1.JBOSS logs:server.log
2.Service logs:Common.log
3.Uniportal logs:uniportalcomm
Service issues:
1.JBOSS logs:server.log
2.Service logs:Common.log

Debug Log
snoop files

Produnction version

Logs (${HOME}/log)
BMP node:please collect log under the path $
{HOME}/log/run/ and ${HOME}/log/debug/.
CBP node:please collect log under
the path ${HOME}/log/run/ and ${HOME}/log/debug/. (charge
probme :please feedback 120.500.900 log under the /debug/)
SCP
node:please collect log under the path $
{HOME}/log/run/scp_run.log and $
{HOME}/log/debug/scfdbg_0_1.log.

Use the collect data script in order to collect all the server
information; and send its output
if ti's the system performance problem .please feedback the
oracle awr report and the alart log
also($ORACLE_BASE/diag/rdbms/<DB_NAME>/<SID>/trace/ale
rt_<SID>.log).
use the etrace tool trace the subscriber number and the
feedback the etrace file.
Product Class Product Requested Info.
BSC configuration file
BSC operation log files
BSC product BSC Alarm log file
Trace file
Performance measurement counters

RNP Request Performance measurement counter

BTS product BTS log


RNC configuration file
RNC logs files
RNC RNC Alarm log file
Trace file
Performance measurement counters

NodeB product NodeB main board log


Wireless

Version +patch
performance task (*.csv)
autostar report
M2000 product Alarm log
Traces file
explorer logs
print screen of the error messages
PCU info folder through PCU info tool
pcu.ini--configuration file
PCU
Alarm History
Network Topology
Trace file .mrf
WASN DBS
WASN DBS configuration file
service log file .srv
How to get
command:EXP CFGMML
command:COL LOG
\bam\common\fam\trace
\bam\version a\ftp\MeasResult

BSC BAM--M2000 Client

command: STR BTSLOG,


path:\bam\common\ftp\bts\btscmplog>
command:EXP CFGMML
command:COL LOG
\bam\common\fam\trace
\bam\version a(b)\ftp\MeasResult
Collecte Via NodeB LMT,
Service > Software Management > Other File
Transfer.
Collecte Via M2000,
Software > Browser > NE > Server

Trace collection tool//OMC Autostar tool

PCU info tool

M2000 Client
M2000 Client
Product Class Requested Info.
Hybrid
Hybrid -Powercube1000V3.2
TP48300/A
Power
TP48200A
TP48600A
Solar
History alarm of hybrid controller
The version of hybrid controller
The type of hybrid controller
power1000 Installation date
Total Power consume of the DC loads
DG average running hours per day
Quantity of issue sites
Battery voltage/battery current/battery brand/battery type
Battery status
Total solar current
alarm information (active and history)
power2000
Controller type and version
quantity of PV modules
load current
SSU status
AC input voltage and current
DC bus bar voltage,load current
Batteries work status
Rectifier status(voltage,current,limit,if out)
Power3000
Monitor status
Alarm information(history and local)
Environment temperature and batteries temperature
Input mains type
Material Delivery Date
Material BOM Code
Material Installation Date
ITS1000 Equipment type
Entironment temperature
Alarm history and statistics
Pictures On Site
Material Delivery Date
Material BOM Code
Alarm history and statistics
Entironment temperature
ITS1000M
Equipment type
Material Installation Date
Pictures On Site
ITS1000M

Equipment Power Consumption

Das könnte Ihnen auch gefallen