NAM Reporting

[CorruptedLogic]

We recently installed a NAM in our new Cat6500. Sicne then, i've been able to track traffic and filter out a few jabbering NIC's and fix SMB traffic problems. However, around 60% ofo ur total network traffic is defined as "Other" traffic in the NAM (as opposed to icmp, ip, smb etc). Is there a way to interpret what this "other" traffic is?..or do i just live with it?

TIA...

 

[jd0gg]

How are you finding that 60% of your traffic is defined as "Other"? Are you looking at the cumulative data? If 60% of your traffic is other, this is probably odd. Usually, "Other" is data link layer traffic, that is broadcasts. This amount of broadcasts is something to investigate. It could be that you have a special protocol that the NAM module just doesn't recognize, but I think that would be unlikely to take up 60% of your traffic. My network is approximately 90% TCP, and the rest is UDP, ICMP, other...

 

[CorruptedLogic]

Sadly, the data i'm looking at is realtime data..as i type, its at 54% of total traffic. as far as i'm aware, we should have no "special" protocols on the network. The only other "high ranking" protocols are Citrix ICA traffic, icmp, SMB and http (all of which i'd expect to see!). Is there any way of defining a custom filter to capture the packets of the "other" traffic? I looked but i can only see options to specify a particular protocol, which is kinda hard to do when i don't know which protocol is the "other" traffic.

Any help would be much appreciated!