Support for IOS 15.3 on ASR

Is there any news regarding this FR??

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 this case.  I still like this product more than Cisco's Prime Management for SLA reporting, when it works.  This is a big issue though.  Cisco owns the biggest slice of the enterprise network hardware space by a large margin.  Cisco's ASR family of routers are the product of choice and for the foreseeable future.  So, in the Cisco centric WAN edge, where degradation to multimedia VoIP and video collaboration is mostly going to occur, Solarwinds will have to reinsert themselves as a viable product for managing the real world performance of traffic.  This will take fixing: 1) ASR and beyond SLA management:  it is doable, just not there  2) adding usability to IP groups in NTA:  all other vendors have a way to manage IP groups (groupings of networks or addresses), but give you the ability associate multiple interfaces of which report flows to correlate.  We need to be able to one-click report on an IP groups usage without needing to aggregate data or worry about double dipping of flows 3) bring NTA into the modern realm by unleashing full Flexible Flow attribute reporting capacities to report and manage appliance performance. 4) holistic network visibility, understand the path from device A to device B and correlate NPM, NTA, and VQNM reporting to assist in identifying and maybe one day automating the remediation of the issues in that space between.  This is where the world of application performance centric network is heading.  Solarwinds has the right team to get it done, just need someone to turn the ship back towards innovation.

Thanks casanave, this is what we had already put in place. Unfortunately it takes more time and also de-values solarwinds as the one stop place for managing IPSLA. Which has led to reduced buy in from departments to continue using Solarwinds. I also agree that it's not Solarwinds fault, unfortunately perception is hard to shift.

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.

Raised this with Solarwinds support and they have come back stating it is a Cisco issue and they can do nothing. Does anyoe have any good contacts at Cisco that they can push this MIB issue?