Network slow when access to web application

Answered Question
Aug 28th, 2007

Hi Experts,

I am trying to figure what i can do on the troubleshooting side to see if the problem is on network or apps or wat..

Well, what i have done is to capture the tracert and did a netstat -a. Did a sniffing as well but not sure how to go about the data.

Any other things that i can do to isolate this network slowness?

Correct Answer by JORGE RODRIGUEZ about 9 years 5 months ago

Cindy, when you say "network slow when access to WEB APP " it is very broad term.. but usually when users complain about an APP being slow they say the network as a whole, is this the case? only the APP ? are other services slow such as mail, internet etc..

Lets assume is the APP only, what you would want is to start at the bottom and start ruling out from the physical aspect and end at application "APP SERVER", one by one. Most secenarios at least in my experience when APPs are slow they either have port speed duplex miss match or the database seating behind it is in another IP subnet, or the server is no match to the amount of internal/external queries.

first check APP port connections on switch ports, check if APP have NICs teaming and or if switch port connections are channel ports, look for eny indication of crc, runts, giant errors on its switchport. If all physical is good then move forward, get the server guys do some homework as well in geting server utilization stats if any.

for catos switch: get the APP MAC address

and locate the switch port the server connect to and look for errors.

If catos:

show port 4/12 ( Module 4 port 12 )

If IOS:

show interface fastethernet#

also look at switch logs

e.g

" show log " for IOS switches

" show loggin buffer " for catos switches

check for any indication of flapping interfaces usually uplinks and connections to the uptream routers.

also check switches and routers cpu processies and see how busy they are.

e.g

"show process cpu " for IOS devices

"show proc cpu " for catos devices

check upstream connection ports to routers and ensure there are not errors on those ports.

If all these above check ok then you can start thinking it is the APP that is having issues and not your network.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
JORGE RODRIGUEZ Tue, 08/28/2007 - 21:06

Cindy, when you say "network slow when access to WEB APP " it is very broad term.. but usually when users complain about an APP being slow they say the network as a whole, is this the case? only the APP ? are other services slow such as mail, internet etc..

Lets assume is the APP only, what you would want is to start at the bottom and start ruling out from the physical aspect and end at application "APP SERVER", one by one. Most secenarios at least in my experience when APPs are slow they either have port speed duplex miss match or the database seating behind it is in another IP subnet, or the server is no match to the amount of internal/external queries.

first check APP port connections on switch ports, check if APP have NICs teaming and or if switch port connections are channel ports, look for eny indication of crc, runts, giant errors on its switchport. If all physical is good then move forward, get the server guys do some homework as well in geting server utilization stats if any.

for catos switch: get the APP MAC address

and locate the switch port the server connect to and look for errors.

If catos:

show port 4/12 ( Module 4 port 12 )

If IOS:

show interface fastethernet#

also look at switch logs

e.g

" show log " for IOS switches

" show loggin buffer " for catos switches

check for any indication of flapping interfaces usually uplinks and connections to the uptream routers.

also check switches and routers cpu processies and see how busy they are.

e.g

"show process cpu " for IOS devices

"show proc cpu " for catos devices

check upstream connection ports to routers and ensure there are not errors on those ports.

If all these above check ok then you can start thinking it is the APP that is having issues and not your network.

cindylee27 Wed, 08/29/2007 - 18:35

Jorge,

Your explaination is really good isolation of the network troubleshooting..:) Never though of this.. Thanks! n rated your post for this..

Any others have insights on this?? :)

Regards,

Joseph W. Doherty Wed, 08/29/2007 - 19:10

"Any other things that i can do to isolate this network slowness?"

When running down a slow network app, you often want to determine whether it's really the network, or something else like a host or server issue.

Traditionally, we start with simple tests like ping and traceroute, which show latency and that you can reach the far side. This is good, but some network problems only show under stress.

So, find some tool or tools that you like that can stress the path between the hosts. If this tool shows unexpected problems, you then can focus on the items Jorge mentioned.

Actions

This Discussion