cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

266
Views
10
Helpful
3
Replies
Beginner

General question regarding troubleshooting method/approach

Hello.

 

This is a general question regarding troubleshooting approach.

 

Suppose there is a problem like this: some mainframe computer tries to transfer 1000 files to a SQL server and occasionally a database application displays error saying that there was some kind of failure with network and some part of those 1000 files is not delivered. This has been going on for a week or so. SQL people are thus convinced that there's some malfunction within the network infrastructure and asks network people to investigate.

 

Let's say that there are 12 hops between source and destination and a networking guy must do initial troubleshooting using only command line commands, wthout any third party network analyzing/monitoring tools (and without using debugging).

 

What commands whoud you use to determine if there is actually something wrong with network?

 

What I would use:

 

1. Traceroute from source to destination to check latency.

2. Ping from source to destination to check packet loss.

3. Check the interfaces directly connected to source and destination devices and see if there is increasing count of errors. Also check if there are some logs regarding the interfaces.

 

Anything else to check for an initial troubleshooting? As I mentioned, there are 12 hops between source and destination - would you login to each of those 12 hops and check all involved interfaces if they contain some errors and also check logs?

 

I do realize that if SQL application throws some error with the phrase "network failure", it does not necessary mean that the problem exist somewhere in networking devices and not in the SQL server itself. But in this case I still need to convince non-network people that from the networks side everything is OK.

 

Thank you.

 

 

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Beginner

Re: General question regarding troubleshooting method/approach

All the above.  I would also set up an SLA with standard ICMP echo parameters from the first hop router to last hop router (and vice versa just in case) making sure it logs any drops.  Right after a transfer failure, check the logs and SLA statistics for SLA failure. 

3 REPLIES 3
Beginner

Re: General question regarding troubleshooting method/approach

All the above.  I would also set up an SLA with standard ICMP echo parameters from the first hop router to last hop router (and vice versa just in case) making sure it logs any drops.  Right after a transfer failure, check the logs and SLA statistics for SLA failure. 

Highlighted
Beginner

Re: General question regarding troubleshooting method/approach

Thank you.

So you wouldn't login into each 12 devices along the path to check interface errors/logs?
Beginner

Re: General question regarding troubleshooting method/approach

I definitely would log into each router and check interface stats. 

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards