ICL Troubleshooting

This is unofficial document, only to be used by people handling GPRS in ICL, Delhi. It is open to all for further edit.
GPRS Connectivity Troubleshooting

Specific to Idea Cellular Limited, Delhis GPRS Network This is an unofficial draft document
NOKIA
Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy
Objectives
The objectives is to provide with guidelines for troubleshooting in case of GPRS connectivity problems. Also provided are examples for available tools.
NOKIA
Generic Details of GPRS Network

There are three APNs defined in our network.

APN1. Internet, it uses dhcp servers to allocate IP Addresses for end/mobile subscribers. APN2. and 3. IMIS and MMSC, these APNs use dhcp server to allocate IP Addresses for MS. However PDP Context can only be activated if its handshake with WAP Gateway is successful. Hence if internet APN works but mmsc/imis doesnot, test WAP gateway. Connectivity to WAP gateway could be checked using ping from both the firewalls.
Know your tools Theres no use in using valuable troubleshooting time to learn the tools, We should know the usage of following tools, before handping, traceroute, nslookup, ethereal packet sniffer, tcpdump, gtpdump, netstat, snoop (on Sun Systems), Log Viewer Be systematic, dont try things first and then think, do it the other way around.
NOKIA
Basic Testing Sequence

Recall or Find out if there have been any changes made in the network Check if GPRS attach is successful Check Subscriber Info. In SGSN Check if SGSN can resolve APN names to Correct IP Addresses (Use ZQRX Command), if not check GPRS DNSs in backbone. Create PDP Context, Check in gtpdump on both the GGSN Check DHCP Servers Log, Use bootpd command with d option (Refer manual provided for more details) If imis/mmsc APN Donot get activated check connections to WAP Gateway from both the GGSN/Firewall, use traceroute/ping Check Log files in WAP Gateway contd.
NOKIA Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy
Contd.
If PDP Context is activated and Internet Access does not Work:
Check Internet Explorer Settings Check Connections from firewall to IT Router on GPRS Subnet Try nslookup from handset/Laptop Try nslookup from firewall Allow on Firewall and try to ping ISP DNS Servers from handset and the firewalls Try to traceroute ISP DNS from both the Firewall
Log all your activities and observations for own analysis. We can test following backward sequence as well, but do not skip steps.
5 NOKIA Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy
Few Suggestions
Keep Current Backups (Not older than two weeks for configuration and one month for OS.) Monitor all interfaces status on GGSN/FW at regular intervals. Since ICL doesnot have NMS for GPRS at this stage, manual and frequent monitoring would be required. Actively monitor hardware/visible alarms on all the NEs. (Donot forget the Cisco Backbone Switch) Ping/ Traceroute all the NEs/IT Servers/Routers at regular interval and check connectivity and status. Someone with sh script know-how can write a simple program as well. Define/Schedule Periodic maintenance tasks for all the NEs in GPRS. The best is to have NMS. Contd..
Contd
Keep a Log/Trace of Working System: Such as

7 NOKIA
gtpdump Log for complete gprs call (All three APNs) Nethawk Log for the complete gprs call Syslog on all the NEs for a day when everything is working fine Configuration Summary Printouts from GGSN/FW/CG Nslookup/ping/traceroute output from handset/laptop/Firewalls to IT Router/ ISP DNSs when system is working fine. Corresponding CDR output of all the calls/logs taken above. Possible Computer Unit Logs from SGSN for a complete call. HLR Profile/SGSN Data of the SIM/Subscriber used for above testing And more such logs..
Few Tools Description - Checking routes

netstat nr will always print out the kernel forwarding table
Destination default 10.0.0.1 10.0.0.2 10.10.192.128/26 10.10.200.0/24 10.20.20.0/24 Gateway 192.168.181.1 tun0c9 10.0.0.2 eth-s1p2c0 10.0.0.2 10.0.0.2 Flags CU CGHU CGHU CGUX CU CU Netif eth-s1p1c0 tun0c9 tun0c9 eth-s1p2c0 tun0c9 tun0c9
The table can also be viewed via the Voyager interface if desired netstat is still the highest authority when verifying routes
NOKIA
route dump (netstat nr)

Destination default 10.0.0.1 10.0.0.2 10.10.192.128/26 10.10.200.0/24 10.20.20.0/24 127.0.0.0/8 localhost 192.168.181.0/24 192.168.181.0 192.168.181.1 224.0.0.0/4 224.0.0.1 240.0.0.0/4 255.255.255.255
Gateway 192.168.181.1 tun0c9 10.0.0.2 eth-s1p2c0 10.0.0.2 10.0.0.2 loop0c0 eth-s1p1c0 eth-s1p1c0 0:60:9:c3:fc:19
Flags CU CGHU CGHU CGUX CU CU BCU CGH CGUX CGHU CGHLU RCU CDHU BCU RCGHU
Netif eth-s1p1c0 tun0c9 tun0c9 eth-s1p2c0 tun0c9 tun0c9 loop0c0 eth-s1p1c0 eth-s1p1c0 eth-s1p1c0
Debugging network traffic

Use tcpdump or gtpdump
dumps ip packets to screen arriving at specified interface may seem cryptic, but isnt all that bad after all options
i <interface> e v vv host <host IP> proto port s <size> interface to monitor include MAC addresses verbose - increased decode very verbose even more decode specify host to monitor specify a protocol to decode. Doesnt support GTP specify TCP or UDP port specify amount of packet to decode
e.g. tcpdump -i eth-s2p3 host 192.168.30.1 gtpdump is same as tcpdump, but with GTP-capability and proper defaults
Default decode
11
NOKIA
Examples
tcpdump for specific interface:
tcpdump -i <interface>
Example showing slot 1 port 1 : tcpdump -i eth-s1p1c0
tcpdump for interface running specific protocol:

tcpdump -i <interface> proto <protocol> Example command to return OSPF traffic: Example command to return IGRP traffic: tcpdump -i eth-s2p3c0 proto ospf tcpdump -i eth-s2p1c0 proto igrp
tcpdump for interface using TCP/UDP application port:

tcpdump -i <interface> port <TCP/UDP application port> Example command to return telnet traffic: tcpdump -i eth-s1p1c0 port telnet Example command to also return telnet traffic: tcpudmp -i eth-s1p1c0 port 23
12
NOKIA
Examples
Filtering Packets Using tcpdump
Not showing specific types of traffic:
tcpdump -i <interface> <ip or udp> <not> <TCP/UDP application port> Example showing no WWW traffic for that interface: tcpdump -i eth-s1p1c0 not port 80
Viewing a portion of the packet: tcpdump -i <interface> -s

<packet size> -vv Example specifying 320 bytes of the packet: tcpdump -i eth-s1p1c0 -s 320 -vv
Viewing a specific IP address: tcpdump -i <interface> host <IP

address> Example specifying only viewing packets with IP address 10.10.10.1: tcpdump -i eth-sp1c0 host 10.10.10.1
Examples
Example showing all RIP traffic for an interface: tcpdump -i eth-s1p1c0 -s 320 -vv port 520 Example showing all OSPF traffic on the ATM link, including LSAs and full information on routes: tcpdump -i atm-s3p1c0 -s 320 -vv proto ospf Example showing all IGRP traffic connected to that interface: tcpdump -i eth-s1p1c0 -s 320 -vv proto igrp Example showing all telnet traffic connected to that interface: tcpdump -i eth-s1p1c0 port 23
14
NOKIA
Monitoring in a switched network

Turn on the Switched Port ANalyzer on the cisco switches. On set-based switches: set span vlan-id|src-port dest-port On IOS-based switches interface xxx (the monitoring interface) port monitor port-to-be-monitored
15
NOKIA
Storing the capture for offline debugging (1/2)

Saving tcpdump results to local file -- Trace file may be generated using tcpdump with the w (write) flag, which stores the packet headers in a local file for later viewing with tcpdump. This feature is useful when you want to e-mail a copy of the tcpdump results to Nokia Customer Service -- The w flag copies the first 68 bytes of every packet, unless the capture size is increased Example which does not display packets: tcpdump -i eths1p1c0 -w /usr/trace.file
Storing the capture for offline debugging (2/2)

NOTE: The file will grow very quickly if the network being snooped is busy. Recommended that you check your drives for the largest amount of free space and store the file there. Remember to delete this file once you are done with it (Press CONTROLC to end capture and print number of packets captured) To send the results via E-mail, you must configure the mail-relay function in the GGSN. To send the file use: mail s some subject receiver@your.org < file
17
NOKIA

ICL Troubleshooting

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ICL Troubleshooting

Încărcat de

Drepturi de autor:

Formate disponibile

This is unofficial document, only to be used by people handling GPRS in ICL, Delhi. It is open to all for further edit.

GPRS Connectivity Troubleshooting

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

Generic Details of GPRS Network

Basic Testing Sequence

Few Tools Description - Checking routes

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

route dump (netstat nr)

Debugging network traffic

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

Example showing slot 1 port 1 : tcpdump -i eth-s1p1c0

tcpdump for interface running specific protocol:

tcpdump for interface using TCP/UDP application port:

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

Viewing a portion of the packet: tcpdump -i <interface> -s

Viewing a specific IP address: tcpdump -i <interface> host <IP

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

Monitoring in a switched network

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

Storing the capture for offline debugging (1/2)

Storing the capture for offline debugging (2/2)

Troubleshooting the elements.ppt/21.6..2000 / Upknowledge Oy

S-ar putea să vă placă și