When doing the set-swisobject I get an access denied error. The account "admin" is marked as an admin in the Orion website.
Is there another location to set permissions that enable read/write on the nodes?
That error message could be improved. Access is denied not because of your account rights, but because updates to IPAM.IPNode are not supported.
Could you tell me more about your use case? What kind of updates would you like to make?
I am trying to use Powershell to update the status and names of IP addresses. For example create a over all process that provisions and IP Address, sets its status to assigned and enters the computer name. All of this in the IPAM.IPNode
Is this a read only node? Is there another way to enter this information?
Thanks
That makes a lot of sense. I don't believe it is possible today, but I have sent this as a feature request to the product manager for IPAM.
Do you know of any other way to achieve this outside of powershell perhaps a webservice call or something?
Unfortunately, no. This feature request is 173733 in our system.
What is the current status of feature request 173733, and how may I follow its progress?
My company has a large deployment of SolarWinds including IPAM, and I am tasked with
automating assignment of certain IPs for new storage servers. I was dismayed to get
all the way past figuring out SWIS CRUD access (through Python with 'suds' SOAP client),
only to discover this thread, implying that all my efforts to this point were useless,
and the only option would be to resort to direct manipulation of the underlying SQL Server
database (which I consider a very bad option, and considered a last resort).
So, where is the feature request now? Has it been implemented? How can I follow the
progress of such features? And, what is the release process for IPAM features?
I am in exactly the same position as Doug. I am trying to allocate IP addresses using SWIS and had gotten to the stage of writing perl code to act on custom properties in the IPAM-IPNodeAttr area of the database.
That fails with an error: (See Below):
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Header><log xmlns="http://schemas.solarwinds.com/2007/08/informationservice">2013-03-01 16:21:01,819 [267] ERROR SolarWinds.InformationService.Core.CrudProcessor - Update operation failed.
System.Security.SecurityException: Access to IPAM.IPNodeAttr denied.
at SolarWinds.InformationService.Core.CrudProcessor.CheckAccessControl(AccessControlOperations operations, EntityType entity, IAccessControlResolver accessControlResolver)
This really is a bummer as we are relying on the IPAM database to provide automation of the IP Addresses in the new "cloud" datacentres.
We will also, have to go back to using the underlying SQL database.
This would be a great thing to get fixed!!!
-- Joel.
Is this now fixed with IPAM API · solarwinds/OrionSDK Wiki · GitHub ?
If so, we are running IPAM 4.5.0 and still getting access denied while running
Set-SwisObject $swis -Uri 'swis://localhost/Orion/IPAM.IPNode/IpNodeId=2' -Properties @{ Alias = 'test1' }
but when running
Get-SwisObject $swis -Uri 'swis://localhost/Orion/IPAM.IPNode/IpNodeId=2'
we are getting the results we expect. Is there permissions somewhere I am missing?
Thanks,
Dustin
When the account was just an IPAM Admin, this would happen, when we made the account a full admin across the board, it was able to do what it needed. Is there other permissions that need to be set with the IPAM 4.5.0 update that enables CRUD actions on the IPAM Module?
Justin
I would have expected it to work as an IPAM admin. Let me check with the IPAM dev team and see if we can figure this out.
Hi,
IPAM API requires Site Admin IPAM account for any not readonly operation including managing IPAM.IPNode entity.
Hope this helps.
Hi yarl,
We had this set for the user prior to turning it into a full Solarwinds Orion Admin, and it was still getting the Access Denied. We had to set this user up as a Full Solarwinds Orion Admin to get the Access Denied to go away.
