topic Re: NBI: configure discovered devices in ExtremeCloud IQ- Site Engine Management Center

NBI: configure discovered devices

jeronimo — Thu, 05 Jan 2023 18:25:07 GMT

Manually configuring discovered devices in the GUI seems to behave differently than using NBI.

Selecting the site
* using GUI (Network > Discovered > Right-click: Configure device > Default Site): all the parameters change as they are inherited from the site
* using NBI: only the site changes and other parameters do not, unless you set them manually

mutation {
network {
configureDiscoveredDevice(input: {
deviceConfig: {
deviceIP: "1.2.3.4",
generalConfig: {
defaultSitePath: "/World/xxx/yyy",

Also, the mutation call does not actually save the configuration, and make ZTP+ progress to the next stage "Pending", and then "Complete".
Which is what hitting "Save" would do in the GUI.

So how do I do using NBI what would happen in the GUI?

1) Select the site and thereby inherit its settings
2) Make ZTP+ actually proceed with provisioning

Re: NBI: configure discovered devices

Robert_Haynes — Fri, 06 Jan 2023 14:43:29 GMT

I will assume the configureDiscoveredDevice mutation simply does not trigger applying Site Actions if the defaultSitePath specifies a specific site. I do know that createDevices mutation did not perform similarly prior to XIQ-SE 22.06 where we added / enhanced it that it would apply Site Actions if an alternative siteLocation was specified.

I would suggest if no other response is provided here to open a case with GTAC for further investigation. This may be a gap in the current design of the mutation you are using.

As for using NBI to trigger ZTP to move to Staged from Pending Edit - I am not aware of such a mutation. Not to say there isn't - but a quick look at the mutation list doesn't show anything obvious. Again - this would be best asked via a GTAC case.

Re: NBI: configure discovered devices

StephanH — Sat, 07 Jan 2023 15:43:19 GMT

Hello Jeronimo,

according to my experience, changes in the site are not automatically written to the devices that belong to the site. This was also confirmed to me by GTAC.

However, there is a call (mutation { network { configureDevice}) that does this.

Re: NBI: configure discovered devices

jeronimo — Mon, 09 Jan 2023 09:30:17 GMT

Thanks, I will have to test if that mutation works before the device has been added i.e. is still in discovery state (ZTP+ pending).

But it probably won't be of much use in this case as we probably can't automate ZTP itself this way.

Re: NBI: configure discovered devices

FlorianMeyer — Mon, 26 Jan 2026 16:49:25 GMT

Hi, may be it's too late. But may be others are interested. I got it working to get the status from "ZTP+ Pending Edit" to "ZTP+ staged" (and then the switch pulls the config... and later ZTP+ completed).

You have to set all required settings (even DNS Servers):

mutation {
network {
configureDiscoveredDevice(
input: {
deviceConfig: {
ipAddress: "1.2.3.4"
ztpPlusConfig: {
configUpdateType: ALWAYS
useDiscoveredMode: DISABLED
domainName: "domain.local"
mgmtInterface: MANAGEMENT_ISID
subnetAddress: "10.20.30.40/24"
gatewayAddress: "10.20.30.1"
configUpdateTime: 1737973036000
ntpServer: "10.10.10.10"
ntpServer2: "10.10.10.11"
dnsServer: "10.10.10.10"
dnsServer2: "10.10.10.11"
}
deviceActionsConfig: {autoAddDevices: true}
generalConfig: {
defaultSitePath: "/World/CAMPUSLAN/TEST"
sysName: "my-fancy-switch-name"
adminProfile: "snmp_v3_profile"
sysContact: "noc@domain.local"

}
}
timeout: 600
operationId: "cfg-1.2.3.4"
}
) {
status
message
operationId
siteLocation
clientSessionId
errorCode
}
}
}