New-PveClusterSdnVnets

Create a new sdn vnet object.

API: POST /cluster/sdn/vnets, Proxmox VE API viewer

Syntax

New-PveClusterSdnVnets
    [-PveTicket <PveTicket>]
    [-Alias <string>]
    [-IsolatePorts <bool>]
    [-LockToken <string>]
    [-Tag <int>]
    [-Type <string>]
    [-Vlanaware <bool>]
    -Vnet <string>
    -Zone <string>
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Alias	string	No	Alias name of the VNet.
-IsolatePorts	bool	No	If true, sets the isolated property for all interfaces on the bridge of this VNet.
-LockToken	string	No	the token for unlocking the global SDN configuration.
-Tag	int	No	VLAN Tag (for VLAN or QinQ zones) or VXLAN VNI (for VXLAN or EVPN zones).
-Type	string	No	Type of the VNet. Values: vnet.
-Vlanaware	bool	No	Allow VLANs to pass through this vnet.
-Vnet	string	Yes	The SDN vnet object identifier.
-Zone	string	Yes	Name of the zone this VNet belongs to.

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

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.