Network Management

Unable to add subnets to IPAM with Admin account

The article describes an issue when the user is unable to add subnets to IPAM, even when they have admin rights for the Orion Platform.

First published date

10/26/2018 6:28 PM

Last published date

1/6/2025 4:43 PM

Overview

Unable to add/Edit subnets to IPAM even when account has admin rights in Orion.

The Add / Edit options are greyed out.

Product section

IP Address Manager

Cause

This issue is caused by the user not having the appropriate permissions within the IPAM module.

Resolution

  1. Log in to the Orion Web Console.
  2. Go to Settings > All Settings.
  3. Scroll down to User Accounts, and click Manage Accounts.
  4. Select account with the issue and click Edit.
  5. Scroll down and expand the IP Address Manager Settings.
  6. If the account has Read Only permissions, change these to Admin.

     

  7. Submit.

If the user is set as a Custom user, you need to click the Edit button and ensure the subnet pertaining to the issue has applied the correct Power User or Operator rights.

Note: If the user displays the Admin Role in the SolarWinds Web Console but is still unable to add subnets in IPAM, it is possible the Account Role setting has not updated correctly in the database. The below query may be used to verify if they have the correct role on the database. Make sure that the account role is displayed as SiteAdmin.

  1. Connect to the SolarWinds server.
  2. Open Database Manager from the SolarWinds Platform folder of the start menu.
  3. Select Add Orion Server, then expand the sql server and database in bold.
  4. Right-click the database and select New Query.
  5. Paste and execute the below:
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.


SELECT * FROM [dbo].[WebUserSettings]
where SettingName like '%ipamaccountrole%'

The issue with database entries not changing per role in the web console was addressed in SolarWinds Platform 2023.1. If you are experiencing this issue, please consider upgrading your environment to at least this version.