Set-PveClusterSdnIpams
Update sdn ipam object configuration.
API: PUT /cluster/sdn/ipams/{ipam}, Proxmox VE API viewer
Syntax
Section titled “Syntax”Set-PveClusterSdnIpams [-PveTicket <PveTicket>] [-Delete <string>] [-Digest <string>] [-Fingerprint <string>] -Ipam <string> [-LockToken <string>] [-Section <int>] [-Token <string>] [-Url <string>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Delete |
string |
No | A list of settings you want to delete. |
-Digest |
string |
No | Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications. |
-Fingerprint |
string |
No | Certificate SHA 256 fingerprint. |
-Ipam |
string |
Yes | The SDN ipam object identifier. |
-LockToken |
string |
No | the token for unlocking the global SDN configuration. |
-Section |
int |
No | |
-Token |
string |
No | |
-Url |
string |
No |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.