Prior suggestions range from uploading collecting the device information (serial, pid, sku, an optional label, etc) and manually entering that data into the Active Advisor portal one device at a time, to uploading the devices in a batch using CSV or XML formats. Your comments and suggestions are welcome!

7 people like this idea

A

Andy Gossett

said
about 4 years ago

An API would nice! If we could just perform a web post containing the model number, code version, and serial number to receive back EOL/EOS/contract information then we could write our own applications independent of the Web front end of ciscoactiveadvisor. That would be INCREDIBLY useful... any plans for that?

c

charles klement

said
almost 4 years ago

I agree,

either a defined import format (json, csv whatever) or an api which we could use to post data to the service would be very helpful. We don't typically have workstations with JRE enabled sitting in locations that can access many of our network devices.

Mike Holloway

said
almost 4 years ago

I'm happy to report that a first pass at this feature is nearing completion, and should make out into our production systems within the next couple of releases (generally one every 2-3 weeks) This initial feature will support upload of devices to register them into Active Advisor via an excel file.

A public API for registering/querying devices is still in the planning stages of our backlog at the moment. The API already exists, but will take some work to make it a generally available feature.

A

Andy Gossett

said
almost 4 years ago

Thanks Mike for the update. I notice that there's a recent tool published that also helps with EOL info and contract status. There isn't an official API exposed but perhaps this could be something that we could also leverage?

Mike Holloway

said
almost 4 years ago

Neat tool Andy, I hadn't seen that one yet. It looks like it will tell you if a particular device (via it's serial number) is covered under a contract, even if you aren't entitled to view details of the contract itself.

T

Trent Hewitt

said
over 3 years ago

Hello,

Has there been any update on the manual import?

Trent

Mike Holloway

said
over 3 years ago

Not yet. It's on our roadmap, and is internally nearing feature completion, but I can't yet give a time-frame on when it will be released.

We're also currently testing a Docker-based scanner, which includes it's own java in a self-contained container image. We envisage the ability to trigger scans via "API" calls into the running container, providing a facility to automate device refresh scans on a regular basis.