Transcript KX-NS1000 data collection for error analysis

KX-NS1000 data collection
for error analysis
Panasonic System Networks CO.,LTD.
KX-NS1000 data collection for error analysis
INDEX
1. Overview
2. SysLog collection
3. Error data collection
4. How to confirm the MPR version of NS1000 ?
5. LOGIN Command interface
6. Protocol trace
7. Wireshark capturing
KX-NS1000 data collection for error analysis
1. Overview
KX-NS1000 data collection for error analysis
The scope of this presentation are
(1) method of collection for problem analysis at
system failure, and
(2) other tools for the problem analysis at the
installation.
KX-NS1000 data collection for error analysis
2. SysLog collection
KX-NS1000 data collection for error analysis
How to get SysLog file ?
Step2:
Select “Utilities”
“3. Log”
“2. SysLog”
Step1:
Click “Maintenance” icon
Connect Web-MC.
-> "Maintenance" icon.
-> "Utility"
-> "3. Log"
-> "2. SysLog"
Step3:
Click “Save” button
at the bottom
KX-NS1000 data collection for error analysis
Downloaded file
The downloaded file has the file-name of the
date&time of download it.
For example:
alllog120124_135345.tar.gz
(file was collected at January 24, 2012 13:53:45 )
This file is archived by the Linux standard format
“tar” + “gz”.
If you extract this file, you can see all the necessary
files such as Error Logs and $SYSERR are included
into this archive file.
KX-NS1000 data collection for error analysis
What is SyaLog ?
SysLog is brandnew log data which we could not
see on elder PBX system.
And SysLog would be most important log file to
analyze the system problem of KX-NS1000.
Please try to collect SysLog at any types of the
problem on KX-NS1000.
SysLog is the event log of the Linux OS.
Thus it is not only the log of call-control, and
contains all the events including CTI or Web-MC etc.
KX-NS1000 data collection for error analysis
How much logs can be kept in SysLog ?
The event log size is approximately 2days.
If the system keeps running without restarting, the
elder events than 2days would be automatically
overwritten by newer events in this log.
This time-size(2days) would not be changed by the
call-traffic etc, and is almost constant.
The event log(2days) is switched to the different file
every time when system is restarted.
The 2days' events before the shut-down is stored as
the different files of CF without overwritten by the
events after the reset.
KX-NS1000 stores up to 8 generations of these
event log files in CF.
KX-NS1000 data collection for error analysis
Important notes for One-Look networked system
Please note that this SysLog file is stored in each
KX-NS1000 system at one-look networking.
The SysLog file of Slave system can not be
collected via the Web-MC of the Master system.
For the Slave system, you need to collect them by
logging into directly to the local Web-MC of each
Slave system.
Two approaching to do it.
KX-NS1000 data collection for error analysis
(A) From Master Web-MC.
Go to HOME of Master Web-MC.
Select target Slave unit.
And right click (not left click!).
From the context menu, select maintenance.
You can login to the maintenance of Slave system.
(B) Direct access by using IP Address of Slave.
Even in DHCP mode, you can confirm the current IP Address of Slave
on the Master Web-MC.
(Setup -> Network Service -> IP Address/Ports select Slave at the top
select menu of system, select "Reference" tab, you can see the
current IP address of selecting Slave system)
Please take memo of IP Address of Slave.
Logout from the Web-MC of Master, and login to the Web-MC of Slave
with this IP Address directly.
Select maintenance icon at HOME of Web-MC.
KX-NS1000 data collection for error analysis
3. Error data collection
KX-NS1000 data collection for error analysis
KX-NS1000 is supporting almost same logs of elder
KX-TDA/TDE/NCP.
You can use partially the similar commands /
technique of analyzing data collection for them.
Please refer FAQ70042 etc which is explaining
about it.
KX-NS1000 data collection for error analysis
Requested Data:
1- PBX Trace data. (Indispensable)
- Connect a PC (with HyperTerminal etc) to the PBX via LAN.
- Start text capture function (PC).
- Login the PBX.
2- Detail Symptom (Indispensable)
E.g.
- When the symptom occur
- What the Extension number
- What is the symptom?
- How to recover?
- Type "VER"
Display the software version
3- Basic PBX data (Indispensable)
- Type "TRF S"
Select data trace task
- PBX model (E.g. NS1000NE(G))
- Type "3"
Ditto
- Software version
- Type "8"
Ditto
- System data (DCSYS)
- Type "10"
Ditto
PSN/PSNUK may not access the system, therefore
- Type "11"
Ditto
please get it and zip it.
(- Type "1B"
Ditto <--- In case of CTI problem, type this too. ) - Remote access IP Address and password
- Press Enter key.
(Indispensable)
- All Minor Error Log (by PC programming software)
- Type "MTS"
Start trace
- All Major Error Log (by PC programming software)
Wait the symptom occurs or duplicate the symptom if you can.
- Type "MTE"
Stop trace
- Type "COMDBG E"
PBX internal data
- Type "COMDBG A"
Ditto
- Type "PATHC"
Ditto
- Type "MAP"
Ditto
- Type "VTRALL"
Ditto
- Type "RSMALL"
Ditto
- Type "FBK B"
Ditto
- Type "CCTALL"
Ditto
- Save the trace data (PC)
KX-NS1000 data collection for error analysis
4. How to confirm the MPR version
of NS1000 ?
KX-NS1000 data collection for error analysis
On KX-TDA/TDE/NCF, you could confirm it by the
"Summary" button of "1.Configuration" - "1.Slot".
But on KX-NS1000, you can not see MPR version
on the same menu.
In order to refer the software version, you need to
use followings.
KX-NS1000 data collection for error analysis
MPR software:
Maintenance ->
System Control ->
Program Update ->
Update Program Files
Scroll down
Current version
KX-NS1000 data collection for error analysis
FAX card firmware:
Setup ->
PBX Configuration ->
Configuration ->
Slot ->
Site Property ->
Fax Card
KX-NS1000 data collection for error analysis
5. LOGIN Command interface
KX-NS1000 data collection for error analysis
We sometimes need to use the LOGIN Command to
collect data or to control the hidden settings of the
system.
In UPCMC of KX-TDA/TDE/NCP, you can use it from
ASCII Command menu on UPCMC.
But Web-MC of KX-NS1000 does not have it.
On KX-NS1000, you need to use the telnet
communication software.
(HyperTerminal or Tera Term etc).
For details, please refer the presentation of "Telnet
connection for analysis".
KX-NS1000 data collection for error analysis
6. Protocol trace
KX-NS1000 data collection for error analysis
Web-MC of KX-NS1000 is supporting same Protocol
trace of the digital/IP communication which is
supported by UPCMC of KX-TDA/TDE/NCP.
QSIG/ISDN Protocol Trace.
V-IPGW16 Protocol Trace.
V-SIPGW Protocol Trace.
CS Status Monitor.
They are almost same of
KX-TDA/TDE/NCP.
KX-NS1000 has additionally following trace data
collection also.
FAX - Protocol Trace.
FAX - Task Sequence Trace.
UM System Trace(Internal).
"UM System Trace" is almost same
functionality of the PUTD/PUTG
Command of KX-TVM/TVA Utility
Command.
KX-NS1000 data collection for error analysis
7. Wireshark capturing
KX-NS1000 data collection for error analysis
KX-NS1000 is also supporting the port-mirroring
function in order to perform the packet capturing by
the PC connected to the maintenance port.
On KX-TDA/TDE/NCP, we needed to use the telnet
communication software (HyperTerminal or Tera
Term etc) in order to activate this function.
But on KX-NS1000, we can easily activate it from
the Web-MC.
Maintenance
wireshark
LAN
KX-NS1000 data collection for error analysis
Setup
Network Service
-> 1.IP Address/Ports
-> Advanced Setting tab
-> Port Mirroring
KX-NS1000 data collection for error analysis

Thank you very much!
Modification：
20120307-01 data collection for error analysis.ppt
- 1st release
20120330-01 data collection for error analysis.ppt
- 2nd release modify “SysLog Collection” “Error Data Collection”