setting adminprofile using NBI

[Salva_ferrer]

Hello,

I have a few 100's of devices configured in site engine with the wrong Access profile (wrong cli credentials) and and few 100's with the correct one, instead of checking one by one which one is right and which one wrong I plan to use a script to try a connection and if it fails, change the access profile to the right one.

But I cannot find the right mutation to do it. I can find the access profile with:

{network{device(ip: "10.36.95.2") {
deviceData{profileId}
}}}

Profileid returned is the id of the access profile.

Then I try to change it to the right one using:

mutation {
network {
configureDevice(input: { deviceConfig: {ipAddress: "10.36.95.2", generalConfig: {adminProfile: "Acceso_Snmp_V3_No_Radius"}}}) {
clientSessionId
errorCode
message
operationId
siteLocation
status
}
}
}

I tried using a profile id and the profile name, it always returns a success but the value never changes in the UI.

I also tried;

mutation {
network {
configureDevice(input: {enforceSystem: true, deviceConfig: {ipAddress: "10.36.95.2", generalConfig: {adminProfile: "Acceso_Snmp_V3_No_Radius"}}}) {
clientSessionId
errorCode
message
operationId
siteLocation
status
}
}
}

In case I needed an enforce to commit changes. The second one always returns an error.

Is there an NBI way to change the access profile of a device in Site ENgine?

regards

Salva

[Robert_Haynes · Accepted solution]

The mutation above to change the profile works for me; 25.02.10 as tested. I successfully changed a profile to another. What I don't see is XIQ-SE attempt to perform a rediscovery triggered by the change of the Poll Type / Admin Profile which is something it would automatically do if one changed the Poll Type / Admin Profile via the GUI.

Try the reloadDevices mutation @ https://extreme-networks.my.site.com/ExtrArticleDetail?an=000121952

mutation {
network {
reloadDevices(input: {devices: [{ipAddress: "10.36.95.2"}]})
}
}

[Salva_ferrer]

Robert, you are right and I'm deeply embarrased. The error in my approach is that the customer broke the naming convention for the destination profile and I blindly wrote what should have been the name instead of the actual name, so I was using the wrong profilename. A double check to the admin profiles names was enough to discover my mistake.

It would be nice to have the API return some kind of errors in those cases. Other than that, I'm the root cause of my own mistake.