- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- monitoring per-Vlan traffic on Procurve 3500yl. Im...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2012 10:12 AM - edited 10-20-2012 10:22 AM
10-20-2012 10:12 AM - edited 10-20-2012 10:22 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2012 02:30 PM
10-20-2012 02:30 PM
Re: monitoring per-Vlan traffic on Procurve 3500yl. Impossible?
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2012 08:58 AM
10-23-2012 08:58 AM
Re: monitoring per-Vlan traffic on Procurve 3500yl. Impossible?
CCIE Service Provider
MASE Network Infrastructure [2011]
H3CSE
CCNP R&S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2012 10:14 AM
10-23-2012 10:14 AM
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.