Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 309
  • Last Modified:

Netflow? (or any way to monitor bandwidth)

Ok, someone has been eating all of our bandwidth this week.  I have a t1 to the internet, connected to a 2621, with a pix 515e behind it.  

The 2621 reports net flow stats back into my network
I need to find a way to do the same at the Pix.  

I am not having any luck tracking the internal users using all of our bandwidth, when I look at the router's netflow output. By the time it hits the router, it is already natted.  I'd like to do some type of monitoring on the Pix. is this possible? I'm running 8.0(3)
0
dissolved
Asked:
dissolved
  • 4
  • 3
1 Solution
 
Voltz-dkCommented:
The PIX doesn't have net flow, but doesn't the net flow information you get from the router include ports?

If you have the live source port, it's trivial to find the mapping..

sh xlate gport <port#>
---
If that doesn't help.. what info DO you have from the router's netflow?  Like how common is the destination port(s) in use?

If you have syslogs at level info+, the PIX will record how many bytes was spent when it closes a connection.  Feeding that through some parsing tool can nail it as well.
0
 
dissolvedAuthor Commented:
yea we're syslogging all of our devices at informational. What do I look for ?
thanks for the xlate command, forgot all about it
0
 
dissolvedAuthor Commented:
did the sh xlate command. Which is the source port which is the the dest port?
67.133.189.200(18293)   Local 172.16.1.84 (4084)

Does this mean 67.33.189200 is listening on port 18293 and sending to 4084 of 172.16.1.84?
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Voltz-dkCommented:
sh xlate just shows translations, for outbound connections they don't show the destination port.
Above is likely such a connection.. 172.16.1.84 is an internal machine, making a connection to the outside from source port 4084.
That connection is then translated to the other port you see, and would likely be the source on your net flow.

If you wanted to see where it goes, "sh conn port 4084" should tell you.

And if you have an idea this is the "top-talker", perhaps from mapping the source port from the routers net flow, you could try:
"sh conn addr 172.16.1.84"
---
It will be hard to manually search syslogs, unless it's real spammy.  But you generally would look for those lines including "Teardown". Like this:

%ASA-6-302014: Teardown TCP connection 102153 for outside:x.x.x.x/110 to inside:192.168.0.10/1561 duration 0:00:00 bytes 1909 TCP FINs
---
I don't know if the PIX supports threat-detection, but that would be another option to track it down.  It's hard on memory though which may be particularly problematic on PIX.
0
 
dissolvedAuthor Commented:
so the ports shown are source ports, got it.   I guess I will try this way, thanks
0
 
dissolvedAuthor Commented:
ok, I see traffic in netflow. It shows the outside address of my firewall, talking to another public IP.

However, when I go in the firewall and do a sh xlate, i do not see these ports. Basically, I can see what traffic is using my bandwidth, along with the destination host (all via netflow)

when it comes down to finding the offending host on my site, I'm not having any luck. this is where I need help
69.2.166.75:23187    destination ip: 67.133.189.200    dest port 3906
 
67.133.189.200 is the outside address of our firewall. 69.2.166.75 is some host on the internet one of my internal users is communicating with.
 
How do i find out the internal user

Open in new window

0
 
Voltz-dkCommented:
Well, first thing to try (if there is a connection right this moment it will work) is:

sh conn addr 69.2.166.75
---
If you have no luck with that, just search your daily logfile.  I don't know if you syslog is on Window or Unix, but use either find or grep respectively.
For example:
find "69.2.166.75" Syslog-090410.txt
or
grep 69.2.166.75 Syslog-090410
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now