I still have no idea what the problem actually is...
Sent from BlueMail
On 28 Sep 2016, 15:36, at 15:36, Talk Jesus chad@talkjesus.com wrote:
There are about 15 VLANS on the second switch. That trunk is needed. I'm at a lost why total utilization doesn't come close in Observium to the upstream. My goal is to figure out where the hiccup is in my configuration. I stopped polling all the VLANS and started polling strictly the port interfaces instead to see if that helped a bit, but it didn't. I also stopped polling that uplink to switch #2. Didn't help strange enough.
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Michael Sent: Wednesday, September 28, 2016 4:32 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Bandwidth Reporting Off
Now as a result VLAN2155 (total utilization) is calculating not
only #1 and #2 drops from the upstream, but even the trunk port labeled “Uplink to Switch #2”.
The "problem" will be that your switch is returning the vlue for the vlan in that way. Observium is not summing the interfaces together, it is the switch that's doing it.
The problem from what I can tell is that you don't believe that traffic from vlan 2155 should be traversing your trunk interface. What are the devices on switch#2 that are participating in vlan 2155? If there are truly none, you coud always prune the vlan form the trunk to be certain; but I don't believe that is the case.
It was never like this until a hired tech reinstalled Observium after
changing Cisco equipment. It always matched the upstream provider nearly 100%
There's a lot more to this story that you haven't told us and just assumed it's all the fault of Observium. All I hear is it worked perfectly until you replaced the switches.
Michael
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
