'The optional lower-bound of the destination port filter condition. If only a single port value is required, then IPDstPortStartMatchCondition and IPDstPortEndMatchCondition must match. If the destination port filter condition is not required, set both fields to zero.'
IPDstPortStartMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The optional destination IP prefix filter condition. Where applicable, both the source and destination prefix families must match. Examples of valid prefixes: 192.168.1.1, 192.168.1.0/24, or fe80::1001:2046/128'
IPDstPrefixMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The IP well-known port filter condition. This matches either the local port number or the remote port number of a supported IP connection. This type of filter is especially effective if the port number is a well-known number assigned by the IANA. If the value of this field is non-zero, then all the following fields are ignored: IPSrcPrefixMatchCondition, IPSrcPortStartMatchCondition, IPSrcPortEndMatchCondition, IPDstPrefixMatchCondition, IPDstPortMatchCondition, and IPDstPortEndMatchCondition.'
IPPortMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The IP protocol filter condition. If set to 0, then all the following fields are ignored: IPPortMatchCondition, IPSrcPrefixMatchCondition, IPSrcPortStartMatchCondition, IPSrcPortEndMatchCondition, IPDstPrefixMatchCondition, IPDstPrefixMatchCondition, and IPDstPortEndMatchCondition.'
Values
['N/A', 'TCP', 'UDP', 'Both']
IPProtocolMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The optional lower-bound of the source port filter condition. If only a single port value is required, then IPSrcPortStartMatchCondition and IPSrcPortEndMatchCondition must match. If the source port filter condition is not required, set both fields to zero.'
IPSrcPortStartMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The optional source IP prefix filter condition. Where applicable, both the source and destination prefix families must match. Examples of valid prefixes: 192.168.1.1, 192.168.1.0/24, or fe80::1001:2046/128'
IPSrcPrefixMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The NetworkDirect port filter condition. This filter is only applicable if the Data Center Bridging server feature is installed. Otherwise, the policy is effectively no-op.'
NetDirectPortMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The optional match condition template that, if specified, overrides all other match conditions with predefined conditions. For example, the iSCSI template has a predefined match on TCP well-known port 3260.'
'The optional URI filter condition. This condition may only be combined with the URIRecursiveMatchCondition, IPDstAddressMatchCondition, IPDstPortStartMatchCondition, and IPDstPortEndMatchCondition fields.'
URIMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'This filter condition supplements URIMatchCondition. If set, the URI match happens for all resources with the base path indicated by URIMatchCondition. Otherwise, a match only happens for a resource with the exact URI.'
URIRecursiveMatchCondition property is in 1 class (MSFT_NetQosPolicySettingData) of ROOT\StandardCimv2\MS_409 and in 2 namespaces
'The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.)'
'Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. For DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.'