HPE Aruba Networking & ProVision-based
1833625 Members
3638 Online
110062 Solutions
New Discussion

monitoring per-Vlan traffic on Procurve 3500yl. Impossible?

 
cameramonkey
Occasional Visitor

monitoring per-Vlan traffic on Procurve 3500yl. Impossible?

We have been monitoring per-port utilization via SNMP using Solarwinds NPM on our 3500yl and it works great.

 

On the switch port that our carrier delivers our main MPLS wan link, the carrier has connected a virtual cloud network. Now that we are passing up to 30mbits to the cloud on top of the 10mbits we originally monitored to the MPLS network, the actual utilization of each is impossible to separate.

 

We broke out the traffic into two unique tagged VLANs. Solarwinds can see the new VLANs. Unfortunately we are not seeing any traffic being reported by the switch on the vlan interfaces and are back to square one.

 

Is there a way to monitor the per-vlan traffic in real time? Is there another OID that we need to monitor? A super secret squirrel command we need to issue at the CLI? Are we screwed?

3 REPLIES 3
paulgear
Esteemed Contributor

Re: monitoring per-Vlan traffic on Procurve 3500yl. Impossible?

I've never found a way around this, regardless of what network monitoring tool i've been using. I never put a lot of time into investigating, but i assumed it was just a limitation of the ProCurve & Comware operating systems that they couldn't feed per-VLAN stats to SNMP. It works great on my Cisco equipment.
Regards,
Paul
Fredrik Lönnman
Honored Contributor

Re: monitoring per-Vlan traffic on Procurve 3500yl. Impossible?

Im pretty sure you cannot get this info out via SNMP, as there are no VLAN counters in the CLI either. Maybe sFlow?
---
CCIE Service Provider
MASE Network Infrastructure [2011]
H3CSE
CCNP R&S

cameramonkey
Occasional Visitor

Re: monitoring per-Vlan traffic on Procurve 3500yl. Impossible?

I'm sure I can do it in sflow, but that defeats the purpose of our HUD. The carrier has offered on-demand access to their Cacti server to run reports on their ports, but it still doesnt solve the problem.

 

We run Orion NPM in "top 10" mode on several displays in our area for near real time traffic on all of our interfaces across our WAN on a single pane of glass. Its not uncommon for to look up and notice odd traffic patterns that alert us to problems 5 minutes or more before our users notice and start complaining. Often we can preemptively stop the problem before it impacts the network.

 

Using sflow would mean having a second screen just for those two interfaces or make us redesign our own custom display page that combines the  top 10 interfaces and sflow graphs. (no small task)

 

We've had this visibility for several years, and arent ready to throw it away just because its not convenient for the carrier.

 

I submitted a ticket to support, and depending what they say I may just have to move to plan b with the carrier.