Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Donnie-C
Community Record
6
Posts
0
Kudos
0
Solutions
Badges
Jun 3 2021
5:51 PM
True, they are different scales but I guess the point I didn't focus on was the "data point length". The surge in data is only about 2 minutes long (shown in uplink) and becomes invisible in the client graph. It would be great if we could highlight a section of the client graph and "zoom in" ... which would expose peaks in data usage that are very important. The client graph is actually hiding important data although it's very useful for drilling into specific client usage. This particular business client is on the outskirts of town so fiber is extremely expensive ... but up until recently I wasn't too concerned about bandwidth constraints since the client graph didn't show us bumping up against the 25Mb/s limit. However, monitoring the uplink graph for a full day shows a very different story. Thanks for the input cmr.
... View more
Jun 3 2021
2:44 PM
Can someone shed some light on why I'm seeing a difference between the client data statics and real-time uplink traffic graphs. I searched the forum and saw reference to both but I couldn't find out what would explain the graphs being different. In my mind (which absolutely could be wrong), I would expect the "clients" graph to be an aggregation of all data from the clients going through the MX64. And uplink traffic would be the same although not broken out by individual client devices. We have a fairly flat network with one WAN link. Around 8:27 to 8:29 this morning, I captured uplink traffic and matched it to the client data graph. The client data graph is showing that our network usage is around 8 to 10 Mb/s ... while the Uplink graph is showing 24Mb/s. Shouldn't these totals be closer? Any input would be appreciated. Thanks
... View more
Dec 26 2019
12:04 PM
Yep, mine looks a little different but I believe the configuration is set the way you recommended. I did however notice the "custom pie chart". Maybe after I run fiddler or wireshark, I could plug in some specific hostnames/ip addresses that I "think" may be the culprit. I know this computer accesses a lot of "steam" applications and yet I don't see steam on the pie chart. I've got a hunch that this steam data is being classified as Xfinity TV ... I just don't know why.
... View more
Dec 26 2019
8:15 AM
Well ... again ... I know for certain the computer is not actually streaming Xfinity TV ... Meraki just reports it as Xfinity TV. Our ISP is Comcast which is the same as Xfinity so it's not entirely surprising to see Xfinity show up on a Meraki report. What doesn't make sense is that 150+GB shows up. Technically, all of the data being streamed to every computer could be labeled Xfinity (or Xfinity TV) since it is going through Xfinity's network. But why would Meraki be able to single out EA (gaming) and Youtube among others, yet not be able to identify the bulk of the network traffic. If I were a conspiracy theorist I'd say Comcast/Xfinity is doing something to my data (encapsulating?). So Meraki thinks my actual end communication is with Xfinity ... but it's not. Again, I know for a fact this computer is not streaming movies/tv programs from Xfinity. I may have to put an agent on the computer itself (fiddler, wireshark) in an attempt to better classify data usage on the client. I don't think I've ever had this problem with Meraki devices at work ... they do a pretty good job of breaking down the datastream. It's only when I installed one at home that it failed to classify the bulk of the data.
... View more
Dec 24 2019
5:38 AM
Thanks for the input Philip. The screen shot I provided is in fact from one of the machines that are "generating the traffic". Meraki does a pretty good job of making it easy to find the "data hogs". However, when I "go and inspect those machines" ... Meraki is classifying the bulk of data as Xfinity TV ... and there's no protocol listed. So I can see that this computer in particular is using a lot of data. I can also see that 92GB of the data is from origin-a.akamaihd.net (probably gaming) ... and another 42GB is from YouTube. But the top spot is Xfinity TV at a whopping 151GB. Again, I know he's not streaming TV programs to the computer ... I just can't figure out why Meraki is showing the destination as Xfinity TV with no protocol listed and no port number.
... View more
Dec 23 2019
1:27 PM
This subject has probably has been discussed before but I've been unable to find a thread. In short, my clients are showing a destination of "Xfinity TV" and I'm trying to figure out why. I actually use an MX64 at home and recently stumbled across this ... I don't have any oddness like this at work. Why does Xfinity TV show up as a destination. Basically I have a couple of computers in the house that eat up all the bandwidth ... and naturally Comcast has a datacap of 1TB per month for the household. So I installed an MX64 to find out where the data was going. Interestingly, the Meraki is classifying the majority of the data (189GB in this case) as Xfinity TV. I was expecting EA or Origin or Steam or some other gaming platform. I know the users do not watch TV on these computers ... not sure why I can't get more detail out of the destination. Any thoughts?
... View more
© 2024 Cisco Systems, Inc.
