
Have you guys ever thought of providing a subscription service to allow for automated reports based on PSIRT, Field Notices and EoL/EoS notices? We would find these report very valuable to our organization to know when a new PSIRT alert comes out that specific items are affected by it based on the variables in the PSIRT notification. Our only option right now appears to be Cisco Works LMS to provide this functionality.
Just a thought,
Mike
That's a great idea. We'll reach out to our Cisco contacts to determine if this API is public for 3rd party integration.
If there are others interested in this feature, please chime in to help us prioritize!
Thanks,
This would be a huge value and a great selling point.
You might also check with http://www.parinetworks.com/trial/pnat.htm
This would be an excellent feature and definitely a selling point.
How nice would it be to pull a report from NCM that list EoS/EoL dates for your entire inventory? And one step further (as suggested by the original post), whether the version of code is subject to a PSIRT.
Chris-
I'm not sure that there's an API, per se, as the EoS/EoL notices are typically static pages posted by Cisco (unfortunately not in one place, either).
I really like this idea and we're talking about it in house. Thank you all very much for the input.
--Christine
This one just came up in our staff meeting this week as we are looking at decomissioning CiscoWorks. Three items came up that we need, but do not have with Orion.
Any one of these has a large impact, all three are a dinosaur killer.
Steve Extrand Sr Network Analyst (1) Orion v10 SLX polling engine & Additional Web Server 25500 elements (2) Orion v10 SLX polling engine (3) NTA v7 786 interfaces (3) IPSLA SLAX
Hi Steve -
On item 1 - depending on where you are thinking you'd want that - you could use the custom HTML resource to add a graphic.
Item 2 - we've been looking in to adding this. Are you looking more for something to automatically retrieve this information or just a place to input and store it in your inventory reports?
Item 3 - user tracking - yes, we have gotten lots of requests for this and this is something we have some support for and will be working on further as well.
Let me know if you'd like to have a call about any of these - I'd love to get your insight. Just pm me or write me at christine.bentsen@solarwinds.com.
--Christine
Christine, can you elaborate a bit more on #1?
What Steve is looking for is exactly what we are interested in as well.
Here's a KB on it - http://knowledgebase.solarwinds.com/kb/questions/1862/How+do+I+display+an+embedded+Web+page+into+Orion%3F
It works the same way for NCM. This resource allows you to show an html page as a resource in your Orion application. You can show an image too. Again, this may not be what you have in mind, but it might get you part of the way there.
--Christine
Thanks for the info Christine.
I think we were looking more for what was suggested in the following post.
I do like the custom html resource though, that is something that we can use in other areas.
Hi Christine,
For item 1, the primary use for this today is to see what interface options are on the remote device. I could certainly create a custom HTML to display, for example, a 3800 series router, but that would not, without a lot of effort, show the active interfaces in that router.
Item 2- Automatic retrieval is what we are looking for. I know I can create a custom property and assign it, but it would be a nightmare to try to manually update given the rate that equipment is End of Saled. I would have to dedicate someone just to watch for the end of sale anouncements and update the custom pollers and properties. CW today has the ability to pull all of the EOS data from a database at Cisco, match it against the hardware we have in inventory, then report on it. A EOS report, coupled with some addtional node details would be a wonderful addition to NPM, or NCM.
-Steve
Thanks Steve. I'm tracking both of these as feature requests. I have both of them in the system already - so I've incremented them with all the comments from this thread.
--Christine
We would also like to have the feature of NCM polling Cisco for EOL/EOS etc.
An auto EoL/EoS report is all that is keeping me on Ciscoworks at the moment... I really want to get rid of it as it's quite resource intensive for us and would much rather have NCM.
Hi I am new to Solarwinds. I noticed that this thread began back in 2009. Is the EOL/EOS feature available yet? and if so what version of Orion NPM do i need to use it?
Please advise
Thanks
An auto EoL/EoS report is all that is keeping me on Ciscoworks at the moment... I really want to get rid of it as it's quite resource intensive for us and would much rather have NCM.
This is a well-identified requirement, unfortunately, Cisco's API (CDS) is not publically available (internal and HW partners). This API is necessary to map automatically discovered devices with vulnerability, EOL info...
Hi
I have a suggestion
Why dont we all collaborate and create our own database and is maintained by the SolarWinds community, think of it much like the TOMTOM map share for SATNAV.
As alot of us have CiscoWorks, we could build quite a extensive database today as alot of us have access to Cisco or have access to resellers who we can request that type of data, then we could upload this into a community drive site and moving forward we just add to it when a particular platform or IOS is EOS or EOL.
NCM could then link into this and use it as a lookup table to allow us to create reports based on the kit managed in each others network.
Just an idea
James
Hi I am new to Solarwinds. I noticed that this thread began back in 2009. Is the EOL/EOS feature available yet? and if so what version of Orion NPM do i need to use it?
Please advise
Thanks
Looks like you did it! Cool. Now I have to figure it out how to run it :(. I already have the CCO ID account
If the demo works (unlike the video on the page) we will buy this immediatly. What a great tool and score for Solarwinds if it lives up to the potential.
Hello all--
Development of this tool is still underway and it's official launch is mid-January. Look for the demo video fix then.
Thank you,
DH
Development of this tool is still underway and it's official launch is mid-January. Look for the demo video fix then.
It's end of January. Any update on the launch and demo?
So the launch has happened and the page with video is updated. There is no demo as most folks are used to, just the video.
However, I want to be clear on this tool. The Cisco Discovery Service is a Cisco provided service which is available to Cisco Channel partner to provide network assessments to customers. This API/Portal is NOT open to any Cisco customer who has a CCO account, you must have special permissions enabled on your CCO account in order to access the API/Service for use.
We are providing this tool to Cisco Channel partners as a free tool for them to use in conjunction with SolarWinds NCM to provide these network assessments to customers.
If this is something you are interested in, you can contact your Cisco SE or Cisco Channel Partner if you do business through them and inquire into them about this.
Well, I for one think you have totally missed what we, your customers, have been asking for. Looking back over this thread I think it was perfectly clear that we wanted a tool we could use to identify our EOS/EOL and PSIRT items to facilitate our removal of CiscoWorks in our environments.
This is not what we were asking for- a tool for channel partners to try to score revenue off of us by doing a network assessment.
We purchased NCM primarily for this one task alone, and SolarWinds should have been far clearer that this end product for channel partners was your intention. We have been asking and waiting for 3 years for this particular feature, and at no time during that period did you give any indication this was not in the pipeline for your customers.
Thanks for nothing.
Steve Extrand Sr Network Analyst (1) Orion v10.2 SLX polling engine & Additional Web Server 35500 elements (5) Orion v10.2 SLX polling engine (1) Orion 7.0 NCM DCX (1) Orion 2.0 UDT UCX (3) Orion 3.8 NTA NCX 1500 interfaces (3) Orion 3.5.1 IPSLA SLAX
I think there is some misunderstanding. As Francois pointed out previously, "this is a well-identified requirement for NCM, unfortunately, Cisco's API (CDS) is not publically available (internal and HW partners). This API is necessary to map automatically discovered devices with vulnerability, EOL info..."
We are 100% with you that this would be awesome feature to add to NCM and we would like nothing more than to do so. It would be a huge win for both customers and SWI. Unfortunately, nothing has changed with respect to Cisco's policy around access to this API. It remains for internal and partner use only.
So, we tried to do the next best thing and at least allow this information to be used against the inventory data you're already collecting in your NCM environment. As Brandon noted above, a Cisco reseller partner would need to assist you as you need their CCO account (with special permissions) to run the tool, but it's a step in the right direction.
We will continue to look at other options for getting this data into NCM out of the box.