func Properties(net *object.Network) (*mo.Network, error) {
	ctx, cancel := context.WithTimeout(context.Background(), provider.DefaultAPITimeout)
	defer cancel()
	var props mo.Network
	if err := net.Properties(ctx, net.Reference(), nil, &props); err != nil {
		return nil, err
	}
	return &props, nil
}
func Properties(net *object.Network) (*mo.Network, error) {
	ctx, cancel := context.WithTimeout(context.Background(), provider.DefaultAPITimeout)
	defer cancel()
	var props mo.Network
	if err := net.Properties(ctx, net.Reference(), nil, &props); err != nil {
		return nil, err
	}
	return &props, nil
}
func Properties ( net * object . Network ) ( * mo . Network , error ) { ctx , cancel := context . WithTimeout ( context . Background ( ) , provider . DefaultAPITimeout ) defer cancel ( ) var props mo . Network if err := net . Properties ( ctx , net . Reference ( ) , nil , & props ) ; err != nil { return nil , err } return & props , nil }
// Properties gets the properties for a specific Network.
//
// By itself, the Network type usually represents a standard port group in
// vCenter - it has been set up on a host or a set of hosts, and is usually
// configured via through an appropriate HostNetworkSystem. vCenter, however,
// groups up these networks and displays them as a single network that VM can
// use across hosts, facilitating HA and vMotion for VMs that use standard port
// groups versus DVS port groups. Hence the "Network" object is mainly a
// read-only MO and is only useful for checking some very base level
// attributes.
//
// While other network MOs extend the base network object (such as DV port
// groups and opaque networks), this only works with the base object only.
// Refer to functions more specific to the MO to get a fully extended property
// set for the extended objects if you are dealing with those object types.
Properties gets the properties for a specific Network . By itself the Network type usually represents a standard port group in vCenter - it has been set up on a host or a set of hosts and is usually configured via through an appropriate HostNetworkSystem . vCenter however groups up these networks and displays them as a single network that VM can use across hosts facilitating HA and vMotion for VMs that use standard port groups versus DVS port groups . Hence the Network object is mainly a read - only MO and is only useful for checking some very base level attributes . While other network MOs extend the base network object ( such as DV port groups and opaque networks ) this only works with the base object only . Refer to functions more specific to the MO to get a fully extended property set for the extended objects if you are dealing with those object types .