casanave

Adsmith, I wouldn't go as far as saying it is a Cisco issue. I have teaming partners with Cisco's Prime Management solution. They are able to push the operation / probe configurations without issue to current IOS XE 15.3 (ASRs) / IOS 15.3 (ISR G2s) and manage them. So, this is a crack-able nut, just yet to be cracked in…

Good idea, but what I would be careful on is, Cisco NBAR has been infamous for miss-categorizing traffic. If you look under the hood, most NBAR definitions (PLDMs) solely use port numbers for application recognition. This includes NBAR2. Historically, it isn't very good at detecting the network bad boy protocols that…

I agree, but I think rates or percents would be the most useful graphs for class utilization and drops. Drops per interval and pure data rate per queue / class per interval. Class tuning for most vendors will be purely based on throughput, not volume. So, not sure why graphing per class usage is not available. Even…

If there are not ASRs on both ends, create the probe in one direction from the remote and manually add the ip sla responder command on the ASR.

Team, Did everyone get this resolved?

Update, thanks are much better now!

Solarwinds and IOS XE = broken VNQM. I have been telling them for a couple years now this was an issue and it has fallen on deaf ears. No priority has been given to keeping this product relevant with modern Cisco networking gear. Good luck

We are on Orion Platform HF2, NPM 2019.4. That said, every upgrade has been seriously painful in that SW and their favorite Austin native partner have never been able to pull one off without weeks of pain following a patch. So, we are extremely adverse to believe them we they say "just upgrade, we've had dozens of…

Ok, I went back and looked and see there is a "Top XX" version of this table. 

What version of on VQNM are you using? I have absolutely had great luck doing those same things prior to IOS XE, especially prior to the Cisco IOS 15.2 family. The CBQoS graphing has been hit or miss. Often it works for a while, then tends to break. One thing that tends to break it is making changes that add or remove…

@"jblankjblank" I up vote the need to be able to add corners, and angles, and curves to connecting lines. Auto-connect geometry can just be noisy. I also to think we should be able to decide what renders in a link pill bubble. We often draw maps for customers or other entities where percentages is all we want to convey. It…

Solarwinds struggles with IOS XE. All new Cisco networking products are moving to it, but VNQM simply is not keeping up here - working itself to the not usable for network quality management with Cisco networking gear. This is the case for all models of branch routers, WAN enterprise routers, and modern switches made by…

I believe you will see more support for midsize enterprise solutions after the full/large size enterprise providers are tackled, only because these players in the market only make up about 40% of the total VoIP handsets in the world spread across a dozen or so vendors. That being said, Cisco and Avaya make up all the rest…

Any updates on fixing/adding support for Cisco ASR and ISR 4000 routers (IOS-XE devices) as SLA source devices? I know it is on the list, way down the list.... I think the continued announcements of EoL/EoS for Cisco's ISR G2 family products should be handwriting on the wall to everyone that they are pushing us to ISR 4000…

Sorry guys, that is not available for "High Discards Today" and hence my confusion, as I can do this on other types of charts and tables:

Jamie, We are all in the same boat on this one.... Out of 8 priority fixes for VNQM 4.2 Solarwinds laid out back in early April, this was number 7. They seem to be waiting until their product loses much of its relevance in the Cisco network arena to address this one unfortunately. They actual ranked making prettier zoom-in…

VQNM has no ability to push IP SLA operations to IOS-XE routers, to include ASRs and ISR4000 series. This has been a known shortcoming for a few years. There is a workaround. If the other end of the operation is a non-IOS XE device, create the operation "in one direction" and have the non-IOS-XE device as the source.