1. Request model
[construct information] Construct information includes construct＇s name, construct＇s type(POC/building)．
[ecare number] The ticket build with 400/800 phone.
[version] Version include UC version/U19 version; if the solution includes PC client and mobile client, please feedback the client version; if the solution includes an IP Phone, please feedback IP Phone version and model.
[networking information] The network topology map, include IP address, other net equipment, etc.
[issue’s phenomenon] Describe the issues’ phenomenon and relation call number.
[logs] please refer to chapter 2/3.
2. Getting the log via the LMT tool
2.1. Starting the LMT software
Software interface：
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/03/58bb1caa0720c.jpg
2.2. Add the device
Press <device> -> <Add Device>.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/03/58bb1caa07cc7.png
Set device name, IP(IP means the direction equipment IP address)
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/03/58bb1caa085ba.png
Press “OK”, then the device tree will add a new device.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/03/58bb1cbd21d20.jpg
2.3. Log in to the device
Double click the device under the Device Tree, or right click the device and select “connect”, then the software will show a login dialog.
If you haven’t changed the device password, you can use “username: admin/password: huawei123” to login the device.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1cd040d35.jpg
2.4. Use the command line
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1cd0417ce.jpg
2.5. Catch package capture
1. Press < Log Manage> -> <Call Log>, get into the interface shows bellow:
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1cd04219e.jpg
2. Press <Module Switch Configuration>
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1ce7c7084.jpg
3. Select the module you need, then 'Start Configuration', then you can catch the package capture. For example, we can select the modules: CCM, USAM, CONSOLEGROUP, SIP, SIPTK, SIP Signal.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1ce7c7ae7.jpg
4. Press< Open>, then the log we caught is in the file.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d08457f7.jpg
Notice:
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d084627f.png means that the process of getting the log has started.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d08469e2.png means that the process of getting the log has stopped.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d08472b4.jpg
5. Stop log, press <Module Switch Configuration> -> <Close All Configuration>.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d0847a87.jpg
3. Getting the log via the script
In the case old versions, we don’t have an LMT tool (or the LMT tool can’t work), so you can use the script to collect the log.
1. Use the third-party SSH tool log in in to the U1900/Softco device, then use the su command to enter the super module.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d2336e3c.png
2. Enter the command.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d2337d57.png
3. Stop collecting log commands.
debug set print flag off
4. Copy all the logs, press on the screen, then send them to us.
4. Issue type and the log module needed to be collect
1. E1/T1 trunk issues
Trunk module (PRI, BRI, ISUP, TUP, R2, QSIG, depends on what kind of trunk is in using), RM, CM, CCM, USAM, SIP, SIP Signal.
2. AT0 trunk issues
AT0, CCM, USAM, RM, CM, SIP, SIP Signal
3. SIP trunk issues
SIPTK, USAM, CCM, SIP, SIP Signal
4. Local user number issues
USAM, CCM, SIP, SIP Signal
5. IVR issues
VU, RM, CM, CCM, USAM, SIP, SIP Signal, trunk module (PRI, BRI, ISUP, TUP, R2, depends on what kind of trunk is in using)
6. Voice single pass, voice double barrier
USAM, CCM, RM, CM, SIP, SIP Signal, trunk module (PRI, BRI, ISUP, TUP, R2, depends on what kind of trunk is in using)
Package capture
If the issues are related with an IP Phone or a third party Sip trunk, we also need the package capture.
5. Building the environment for catching the package capture
1. Make port mirror, mirror U19 and all the users’ PC ports to the port which is for catching package capture. Take Hua Wei S3328 for example, mirror Ethernet0/0/2 port (U19 wire line in this port) mirror to Ethernet0/0/16 port:
[Quidway]observing-port 1 interface Ethernet 0/0/16
[Quidway]interface Ethernet0/0/2
[Quidway-Ethernet0/0/2]port-mirroring to observe-port 1 both
2. Setup WireShark.
3. Plug in the PC wire line into the mirrored port (Ethernet0/0/16), open WireShark press 'Capture -> Interfaces'.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d2338644.png
6. Capture cycle
6.1. Build capture cycle environment
1. Make port mirror, mirror U19 and all the users’ PC ports to the port which is for catching package capture. Take Hua Wei S3328 for example, mirror Ethernet0/0/2 port (U19 wire line in this port) mirror to Ethernet0/0/16 port:
[Quidway]observing-port 1 interface Ethernet 0/0/16
[Quidway]interface Ethernet0/0/2
[Quidway-Ethernet0/0/2]port-mirroring to observe-port 1 both
2.Setup WireShark, (advance: don’t use Ethereal, because this software have some problems). Then get into the install directory by 'cmd'.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d495a87e.png
2.Check the PC net dump information, make sure which network card is being used:
dumpcap –D
Search for the network card, then use this card to dump the capture.
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d495b203.jpg
3. Start the capture cycle, for example if the capture’s size is bigger than 100M, it will create a new capture file. The total captures count is 100; if exceed, the new package will replace the old one (this way, the capture will take 10G space in total).
Notice:
The -i network card (find the card index by following Step 2); -w save file name; -b capture cycle; filesize every packages size; files total files count;
dumpcap -i 2 -w D:\aa.pcap -b filesize:100000 -b files:100
http://image.hw3static.com/hi/staticimages/hi3msf/images/2017/0305/04/58bb1d495bb38.png
6.2. MORE HELP：dumpcap -h
---------------------------------------------
Usage: dumpcap [options] ...
Capture interface:
-i< interface> name or idx of interface (def: first non-loopback)
-f <capture filter> packet filter in libpcap filter syntax
-s< snaplen> packet snapshot length (def: 65535)
-p don't capture in promiscuous mode
-B <buffer size> size of kernel buffer (def: 1MB)
-y <link type> link layer type (def: first appropriate)
-D print list of interfaces and exit
-L print list of link-layer types of iface and exit
-S print statistics for each interface once every second
-M for -D, -L, and -S produce machine-readable output
RPCAP options:
-r don't ignore own RPCAP traffic in capture
-u use UDP for RPCAP data transfer
-A <user>:<password> use RPCAP password authentication
-m <sampling type> use packet sampling
count:NUM - capture one packet of every NUM
timer:NUM - capture no more than 1 packet in NUM ms
Stop conditions:
-c <packet count> stop after n packets (def: infinite)
-a <autostop cond.> ... duration:NUM - stop after NUM seconds
filesize:NUM - stop this file after NUM KB
files:NUM - stop after NUM files
Output (files):
-w< filename> name of file to save (def: tempfile)
-b <ringbuffer opt.> ... duration:NUM - switch to next file after NUM secs
filesize:NUM - switch to next file after NUM KB
files:NUM - ringbuffer: replace after NUM files
-n use pcapng format instead of pcap
Miscellaneous:
-v print version information and exit
-h display this help and exit
Example: dumpcap -i eth0 -a duration:60 -w output.pcap
'Capture network packets from interface eth0 until 60s passed into output.pcap'
Use Ctrl-C to stop the capturing at any time.
