- Prime server is used for plug-n-play for configuring 819s. We have about 50 profiles that we use. One of the problems that run into on occasion is that an 819 will be placed in the wrong profile and there is not an easy way of finding which profile it is defined to. So the only way to find it is to open each profile and search for the 819. This takes some time.
- In using some of the GET commands, could see where you can search on the devices IP address, but the returned results does not show which profile the 819 is assigned to. Is there a REST API resource that you can use to identify by IP address which profile a device is assigned to. Using Get Devices does not give this information.
The Prime Infrastructure API supports PnP since 3.1.5. So if you're on 3.1, install the latest maintenance release.
You can check to see if the API resources needed are available by checking the following URLs
https://YOUR_SERVER/webacs/api/v1/op/pnp/profile/%7BpnpProfileFolder%7D-GET?_docs
https://YOUR_SERVER/webacs/api/v1/op/pnp/profile/%7BprofileName%7D/instance/-GET?_docs
If you get valid documentation, then you have the right version and patches applied.
First, get the list of profile names for your devices. Since you're dealing with 819s, the URL to query is
https://YOUR_SERVER/webacs/api/v1/op/pnp/profile/Router
That will return a list of profiles. Extract the profileNames of interest to you.
Next, issue queries for each profile to get back all of the instances of it.
https://YOUR_SERVER/webacs/api/v1/op/pnp/profile/PROFILE_NAME/instance/
The instances should include the device serial number for each device using the profile. You can get from the GET data/InventoryDetails resource, which also includes the management IP of the device.
Comments
0 comments
Please sign in to leave a comment.