vtn-flow-filter

Base Information

prefix	vfilter
namespace	urn:opendaylight:vtn:flow:filter
revision	2015-09-07
description	The module that describes the data models for flow filter, which provides packet filtering feature for packets forwarded in VTN.
yang-version	1
imports	vtype:vtn-types 2015-02-09; vaction:vtn-flow-action 2015-04-10;

Groupings Summary

Name	Description
vtn-redirect-filter-config	Describes the configuration for the redirect flow filter.
vtn-flow-filter-result	Describes pairs of flow filter indices and `vtn-update-type' values. This grouping is used as output of RPC that modifies the flow filter configuration.
vtn-flow-filter-list	Describes a list of flow filters.
vtn-flow-filter-config	Describes a rule of a packet filter applied to packets forwarded in VTN. If a flow condition configured in a flow filter matches a packet, flow actions configured in `actions' are applied to the packet in ascending order of `order' field in each action. - If `actions' is omitted or it is empty, the flow filter is applied to the packet without modifying the packet. - Actions in `actions' field will be evaluated in ascending order of `order' value. - Note that the VLAN ID of the packet cannot be modified by flow action because it is always determined by the virtual mapping configuration, such as port mapping. - `actions' is ignored if the type of the flow filter is `drop'. Only the following flow actions can be configured into `actions'. - `vtn-set-dl-src-action' - `vtn-set-dl-dst-action' - `vtn-set-vlan-pcp-action' - `vtn-set-inet-src-action' - `vtn-set-inet-dst-action' - `vtn-set-inet-dscp-action' - `vtn-set-port-src-action' - `vtn-set-port-dst-action' - `vtn-set-icmp-type-action' - `vtn-set-icmp-code-action'
vtn-flow-filter-id	Specifies the target list of flow filters for RPC. If `tenant-name', `bridge-name', and `interface-name' is configured, the flow filter in the virtual interface attached to the vBridge is targeted. `output' field determines the flow direction for the flow filter. If `tenant-name' and `bridge-name' is configured and `interface-name' is omitted, the flow filter in the specified vBridge is targeted. `output' field determines the flow direction for the flow filter. If `tenant-name', `terminal-name', and `interface-name' is configured, the flow filter in the virtual interface attached to the vTerminal is targeted. `output' field determines the flow direction for the flow filter. If `tenant-name' is configured and `bridge-name', `terminal-name', and `interface-name' are omitted, the flow filter in the VTN is targeted. In this case `output' field is ignored because the VTN has a flow filter only for incoming packets. Otherwise RPC will fail.
vtn-flow-filter-type-fields	Describes the type of flow filter.

RPCs Summary

Name	Description
set-flow-filter	Create or modify the flow filter. This operation takes a list of `vtn-flow-filter-config', and put all configurations into the flow filter list specified by `vtn-flow-filter-id' in the RPC input. Flow filter indices specified in the RPC input will be copied to the RPC output, and `status' field in `vtn-flow-filter-result' describes the result of the operation. Note that a duplicate flow filter index in the RPC input will cause a `BADREQUEST' error. `CREATED' indicates that new flow filter has been associated with the given index number in the specified flow filter list. `CHANGED' indicates that the flow filter specified by the given index number has been modified as specified by the RPC input. Null indicates that the flow filter specified by the given index was not changed. On failure, one of vtn-error-tag value which indicates the cause of error is set into application tag in RPC error. `BADREQUEST' is set if the RPC input contains invalid data. `NOTFOUND' is set if the virtual node which contains the specified flow filter list is not present. `INTERNALERROR' is set if the operation failed due to internal error.
remove-flow-filter	Remove the specified flow filters. Index numbers for flow filters passed to `indices' list in the RPC input will be copied to the RPC output, and `status' field in the RPC output describes the result of the operation. `REMOVED' indicates that the flow filter specified by `index' field in the RPC output has been removed. Null indicates that the flow filter specified by `index' field is not present in the flow filter list specified by the RPC input. If no flow filter index is specified by the RPC input, all the flow filters in the specified flow filter list will be removed. In this case indices of all the removed flow filters will be copied to the RPC output. `flow-filter-result' in the RPC output will be null if no flow filter index is specified by the RPC input and the specified flow filter list is empty. On failure, one of vtn-error-tag value which indicates the cause of error is set into application tag in RPC error. `BADREQUEST' is set if the RPC input contains invalid data. `NOTFOUND' is set if the virtual node which contains the specified flow filter list is not present. `INTERNALERROR' is set if the operation failed due to internal error.

Name

Description

set-flow-filter

Create or modify the flow filter. This operation takes a list of `vtn-flow-filter-config', and put all configurations into the flow filter list specified by `vtn-flow-filter-id' in the RPC input. Flow filter indices specified in the RPC input will be copied to the RPC output, and `status' field in `vtn-flow-filter-result' describes the result of the operation. Note that a duplicate flow filter index in the RPC input will cause a `BADREQUEST' error. `CREATED' indicates that new flow filter has been associated with the given index number in the specified flow filter list. `CHANGED' indicates that the flow filter specified by the given index number has been modified as specified by the RPC input. Null indicates that the flow filter specified by the given index was not changed. On failure, one of vtn-error-tag value which indicates the cause of error is set into application tag in RPC error. `BADREQUEST' is set if the RPC input contains invalid data. `NOTFOUND' is set if the virtual node which contains the specified flow filter list is not present. `INTERNALERROR' is set if the operation failed due to internal error.

remove-flow-filter

Remove the specified flow filters. Index numbers for flow filters passed to `indices' list in the RPC input will be copied to the RPC output, and `status' field in the RPC output describes the result of the operation. `REMOVED' indicates that the flow filter specified by `index' field in the RPC output has been removed. Null indicates that the flow filter specified by `index' field is not present in the flow filter list specified by the RPC input. If no flow filter index is specified by the RPC input, all the flow filters in the specified flow filter list will be removed. In this case indices of all the removed flow filters will be copied to the RPC output. `flow-filter-result' in the RPC output will be null if no flow filter index is specified by the RPC input and the specified flow filter list is empty. On failure, one of vtn-error-tag value which indicates the cause of error is set into application tag in RPC error. `BADREQUEST' is set if the RPC input contains invalid data. `NOTFOUND' is set if the virtual node which contains the specified flow filter list is not present. `INTERNALERROR' is set if the operation failed due to internal error.

Groupings

vtn-redirect-filter-config
- Description: Describes the configuration for the redirect flow filter.
vtn-flow-filter-result
- Description: Describes pairs of flow filter indices and `vtn-update-type' values. This grouping is used as output of RPC that modifies the flow filter configuration.
vtn-flow-filter-list
- Description: Describes a list of flow filters.
vtn-flow-filter-config
- Description: Describes a rule of a packet filter applied to packets forwarded in VTN. If a flow condition configured in a flow filter matches a packet, flow actions configured in `actions' are applied to the packet in ascending order of `order' field in each action. - If `actions' is omitted or it is empty, the flow filter is applied to the packet without modifying the packet. - Actions in `actions' field will be evaluated in ascending order of `order' value. - Note that the VLAN ID of the packet cannot be modified by flow action because it is always determined by the virtual mapping configuration, such as port mapping. - `actions' is ignored if the type of the flow filter is `drop'. Only the following flow actions can be configured into `actions'. - `vtn-set-dl-src-action' - `vtn-set-dl-dst-action' - `vtn-set-vlan-pcp-action' - `vtn-set-inet-src-action' - `vtn-set-inet-dst-action' - `vtn-set-inet-dscp-action' - `vtn-set-port-src-action' - `vtn-set-port-dst-action' - `vtn-set-icmp-type-action' - `vtn-set-icmp-code-action'
vtn-flow-filter-id
- Description: Specifies the target list of flow filters for RPC. If `tenant-name', `bridge-name', and `interface-name' is configured, the flow filter in the virtual interface attached to the vBridge is targeted. `output' field determines the flow direction for the flow filter. If `tenant-name' and `bridge-name' is configured and `interface-name' is omitted, the flow filter in the specified vBridge is targeted. `output' field determines the flow direction for the flow filter. If `tenant-name', `terminal-name', and `interface-name' is configured, the flow filter in the virtual interface attached to the vTerminal is targeted. `output' field determines the flow direction for the flow filter. If `tenant-name' is configured and `bridge-name', `terminal-name', and `interface-name' are omitted, the flow filter in the VTN is targeted. In this case `output' field is ignored because the VTN has a flow filter only for incoming packets. Otherwise RPC will fail.
vtn-flow-filter-type-fields
- Description: Describes the type of flow filter.

RPC Definitions

set-flow-filter

Description: Create or modify the flow filter. This operation takes a list of `vtn-flow-filter-config', and put all configurations into the flow filter list specified by `vtn-flow-filter-id' in the RPC input. Flow filter indices specified in the RPC input will be copied to the RPC output, and `status' field in `vtn-flow-filter-result' describes the result of the operation. Note that a duplicate flow filter index in the RPC input will cause a `BADREQUEST' error. `CREATED' indicates that new flow filter has been associated with the given index number in the specified flow filter list. `CHANGED' indicates that the flow filter specified by the given index number has been modified as specified by the RPC input. Null indicates that the flow filter specified by the given index was not changed. On failure, one of vtn-error-tag value which indicates the cause of error is set into application tag in RPC error. `BADREQUEST' is set if the RPC input contains invalid data. `NOTFOUND' is set if the virtual node which contains the specified flow filter list is not present. `INTERNALERROR' is set if the operation failed due to internal error.

container: input

uses: vtn-flow-filter-id

refines:

uses: vtn-flow-filter-list

refines:

leaf: output

description: Describes the flow direction for the flow filter. If true, the flow filter list for outgoing packets is targeted. If false or omitted, the flow filter list for incoming packets is targeted.
type: (urn:ietf:params:xml:ns:yang:1)boolean

leaf: tenant-name

description: The name of the VTN.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: bridge-name

description: The name of the vBridge. This field is omitted if the virtual node specified by this model is neither a vBridge nor a virtual node attached to the vBridge.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: router-name

description: The name of the vRouter. Currently the VTN Manager never uses this field because the virtual router is not yet supported.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: terminal-name

description: The name of the vTerminal. This field is ignored if `bridge-name' field is configured. This field is omitted if the virtual node specified by this model is neither a vTerminal nor a virtual node attached to the vTerminal.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: interface-name

description: The name of the virtual interface. - If the virtual interface specified by this model is attached to a vBridge, the name of the vBridge is set to `bridge-name' field. - If the virtual interface specified by this model is attached to a vTerminal, the name of the vTerminal is set to `terminal-name' field. - This field is omitted if the virtual node specified by this model is not a virtual interface.
type: (urn:ietf:params:xml:ns:yang:1)string

list: vtn-flow-filter

description: Describes a list of flow filters configured in a virtual node in VTN. Each flow filter in this list needs to have a unique index in `index' field. `index' value is used to determine order of flow filter evaluation. Flow filters in this list are evaluated against packet in ascending order of `index' value, and only the first matched flow filter is applied to the packet.
key definition: index

uses: vtn-flow-filter-config

refines:

leaf: condition

description: The name of the flow condition that selects packets. This flow filter is invalidated if the flow condition specified by this field is not present.
type: (urn:opendaylight:vtn:types)vnode-name

leaf: index

description: The index value that determines the order of elements in a list.
type: (urn:opendaylight:vtn:types)int32

choice: vtn-flow-filter-type

description: Describes the abstract type of flow filter.

case: vtn-drop-filter-case

description: The branch of the `vtn-flow-filter-type' choice for the `vtn-drop-filter'.

container: vtn-drop-filter

description: Describes the DROP flow filter which discards the specified packet.

case: vtn-pass-filter-case

description: The branch of the `vtn-flow-filter-type' choice for the `vtn-pass-filter'.

container: vtn-pass-filter

description: Describes the PASS flow filter which lets the specified packet through the virtual node in the VTN.

case: vtn-redirect-filter-case

description: The branch of the `vtn-flow-filter-type' choice for the `vtn-redirect-filter'.

container: vtn-redirect-filter

description: Describes the REDIRECT flow filter which forwards the specified packet to another virtual interface in the VTN.

uses: vtn-redirect-filter-config

refines:

container: redirect-destination

description: Describes the path to the virtual interface where the specified packets are forwarded. - The VTN name configured in `tenant-name' field is always ignored. The VTN name is always determined by the location of the virtual node that contains the flow filter. - The path to the virtual interface that contains this flow filter cannot be specified. - Note that every packet redirected by the flow filter is discarded if the virtual interface specified by this field is not present in the VTN. Packet redirection should be configured not to cause the packet loop. The number of virtual node hops per a flow (the number of packet redirections) is limited to 100. If the number of virtual node hops exceeds the limit, it is treated as the packet loop and then the packet is discarded.

uses: (urn:opendaylight:vtn:types)vnode-path-fields

refines:

leaf: tenant-name

description: The name of the VTN.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: bridge-name

description: The name of the vBridge. This field is omitted if the virtual node specified by this model is neither a vBridge nor a virtual node attached to the vBridge.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: router-name

description: The name of the vRouter. Currently the VTN Manager never uses this field because the virtual router is not yet supported.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: terminal-name

description: The name of the vTerminal. This field is ignored if `bridge-name' field is configured. This field is omitted if the virtual node specified by this model is neither a vTerminal nor a virtual node attached to the vTerminal.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: interface-name

description: The name of the virtual interface. - If the virtual interface specified by this model is attached to a vBridge, the name of the vBridge is set to `bridge-name' field. - If the virtual interface specified by this model is attached to a vTerminal, the name of the vTerminal is set to `terminal-name' field. - This field is omitted if the virtual node specified by this model is not a virtual interface.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: output

description: Determine the direction of the packet redirection. - If true is specified, the packet is redirected as outgoing packet. + The redirected packet will be treated as if it is transmitted from the virtual interface specified by `redirect-destination'. + A list of flow filters for outgoing packets configured in the virtual interface specified by `redirect-destination' wil be evaluated against the redirected packet. If the packet is passed by the flow filter, it is transmitted to the physical network mapped to the virtual interface by port mapping. The packet will be discarded if port mapping is not configured to the virtual interface. - If false is specified or omitted, the packet is redirected as incoming packet. + The redirected packet will be treated as if it is received from the virtual interface specified by `redirect-destination'. The packet is redirected even if no physical network is mapped to the destination virtual interface by port mapping. + A list of flow filters for incoming packets configured in the virtual interface specified by `redirect-destination' will be evaluated against the redirected packet. If the packet is passed by the flow filter, it is forwarded to the virtual node that contains the virtual interface.
type: (urn:ietf:params:xml:ns:yang:1)boolean

list: vtn-flow-action

description: Describes a list of flow actions supported by the VTN Manager. Each action in this list needs to have a unique index value in `order' field. Flow actions in a flow entry are sorted by `order' field in ascending order.
key definition: order

uses: (urn:opendaylight:vtn:flow:action)vtn-ordered-flow-action

refines:

leaf: order

type: (urn:ietf:params:xml:ns:yang:1)int32

choice: vtn-action

description: Describes the abstract type of flow action.

case: vtn-drop-action-case

description: The branch of the `vtn-action' choice for the `vtn-drop-action'.

container: vtn-drop-action

description: Describes the flow action that drops every packet.

case: vtn-pop-vlan-action-case

description: The branch of the `vtn-action' choice for the `vtn-pop-vlan-action'.

container: vtn-pop-vlan-action

description: Describes the flow action that strips the outermost VLAN tag.

case: vtn-push-vlan-action-case

description: The branch of the `vtn-action' choice for the `vtn-push-vlan-action'.

container: vtn-push-vlan-action

description: Describes the flow action that adds a VLAN tag into packet.

leaf: vlan-type

description: Describes the type for a new VLAN tag.
type: (urn:opendaylight:vtn:types)vlan-type

case: vtn-set-dl-dst-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-dl-dst-action'.

container: vtn-set-dl-dst-action

description: Describes the flow action that sets the specified destination MAC address into the Ethernet header. Node that the following MAC address cannot be specified. - Broadcast address - Multicast address - Zero

uses: (urn:opendaylight:vtn:flow:action)vtn-dladdr-action-fields

refines:

leaf: address

description: Describes the MAC address to be set into packet.
type: (urn:ietf:params:xml:ns:yang:ietf-yang-types)mac-address

case: vtn-set-dl-src-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-dl-src-action'.

container: vtn-set-dl-src-action

description: Describes the flow action that sets the specified source MAC address into the Ethernet header. Node that the following MAC address cannot be specified. - Broadcast address - Multicast address - Zero

uses: (urn:opendaylight:vtn:flow:action)vtn-dladdr-action-fields

refines:

leaf: address

description: Describes the MAC address to be set into packet.
type: (urn:ietf:params:xml:ns:yang:ietf-yang-types)mac-address

case: vtn-set-icmp-code-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-icmp-code-action'.

container: vtn-set-icmp-code-action

description: Describes the flow action that sets the specified ICMP code into the ICMP header. Currently, this action only affects ICMP packet on IPv4.

leaf: code

description: The ICMP code to be set. If this field is omitted, it will be treated as zero is specified.
type: code
default: 0

case: vtn-set-icmp-type-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-icmp-type-action'.

container: vtn-set-icmp-type-action

description: Describes the flow action that sets the specified ICMP type into the ICMP header. Currently, this action only affects ICMP packet on IPv4.

leaf: type

description: The ICMP type to be set. If this field is omitted, it will be treated as zero is specified.
type: type
default: 0

case: vtn-set-inet-dscp-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-inet-dscp-action'.

container: vtn-set-inet-dscp-action

description: Describes the flow action that sets the specified IP DSCP value into the IP header. Currently, only IPv4 packet can be modified by this action.

leaf: dscp

description: The DSCP value to be set. If this field is omitted, it will be treated as zero is specified.
type: dscp
default: 0

case: vtn-set-inet-dst-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-inet-dst-action'.

container: vtn-set-inet-dst-action

description: Describes the flow action that sets the specified destination IP address into the IP header. Currently, only IPv4 address can be specified and this action affects only IPv4 packet.

uses: (urn:opendaylight:vtn:flow:action)vtn-ipaddr-action-fields

refines:

choice: address

case: ipv4

leaf: ipv4-address

type: (urn:ietf:params:xml:ns:yang:ietf-inet-types)ipv4-prefix

case: ipv6

leaf: ipv6-address

type: (urn:ietf:params:xml:ns:yang:ietf-inet-types)ipv6-prefix

case: vtn-set-inet-src-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-inet-src-action'.

container: vtn-set-inet-src-action

description: Describes the flow action that sets the specified source IP address into the IP header. Currently, only IPv4 address can be specified and this action affects only IPv4 packet.

uses: (urn:opendaylight:vtn:flow:action)vtn-ipaddr-action-fields

refines:

choice: address

case: ipv4

leaf: ipv4-address

type: (urn:ietf:params:xml:ns:yang:ietf-inet-types)ipv4-prefix

case: ipv6

leaf: ipv6-address

type: (urn:ietf:params:xml:ns:yang:ietf-inet-types)ipv6-prefix

case: vtn-set-port-dst-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-port-dst-action'.

container: vtn-set-port-dst-action

description: Describes the flow action that sets the specified destination port number into the TCP or UDP header. Currently, this action only affects TCP or UDP packet on IPv4.

uses: (urn:opendaylight:vtn:flow:action)vtn-port-action-fields

refines:

leaf: port

description: Describes the port number to be set. If this field is omitted, it will be treated as zero is specified.
type: port
default: 0

case: vtn-set-port-src-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-port-src-action'.

container: vtn-set-port-src-action

description: Describes the flow action that sets the specified source port number into the TCP or UDP header. Currently, this action only affects TCP or UDP packet on IPv4.

uses: (urn:opendaylight:vtn:flow:action)vtn-port-action-fields

refines:

leaf: port

description: Describes the port number to be set. If this field is omitted, it will be treated as zero is specified.
type: port
default: 0

case: vtn-set-vlan-id-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-vlan-id-action'.

container: vtn-set-vlan-id-action

description: Describes the flow action that sets the specified VLAN ID into the IEEE 802.1Q VLAN tag.

leaf: vlan-id

description: The VLAN ID to be set. Note that zero cannot be specified. If you need a flow action which removes VLAN tag from packets, use `vtn-pop-vlan-action' instead.
type: (urn:opendaylight:vtn:flow:action)uint16

case: vtn-set-vlan-pcp-action-case

description: The branch of the `vtn-action' choice for the `vtn-set-vlan-pcp-action'.

container: vtn-set-vlan-pcp-action

description: Describes the flow action that sets the specified VLAN priority into the IEEE 802.1Q VLAN tag.

leaf: vlan-pcp

description: The VLAN priority to be set. If this field is omitted, it will be treated as zero is specified.
type: vlan-pcp
default: 0

container: output

uses: vtn-flow-filter-result

refines:

list: flow-filter-result

description: Describes a pair of flow filter index and `vtn-update-type' value.

uses: (urn:opendaylight:vtn:types)vtn-rpc-result

refines:

leaf: index

description: One of flow filter indicies specified by the RPC input.
type: (urn:ietf:params:xml:ns:yang:1)int32

leaf: status

description: Describes the status of the RPC result.
type: (urn:opendaylight:vtn:types)vtn-update-type

remove-flow-filter

Description: Remove the specified flow filters. Index numbers for flow filters passed to `indices' list in the RPC input will be copied to the RPC output, and `status' field in the RPC output describes the result of the operation. `REMOVED' indicates that the flow filter specified by `index' field in the RPC output has been removed. Null indicates that the flow filter specified by `index' field is not present in the flow filter list specified by the RPC input. If no flow filter index is specified by the RPC input, all the flow filters in the specified flow filter list will be removed. In this case indices of all the removed flow filters will be copied to the RPC output. `flow-filter-result' in the RPC output will be null if no flow filter index is specified by the RPC input and the specified flow filter list is empty. On failure, one of vtn-error-tag value which indicates the cause of error is set into application tag in RPC error. `BADREQUEST' is set if the RPC input contains invalid data. `NOTFOUND' is set if the virtual node which contains the specified flow filter list is not present. `INTERNALERROR' is set if the operation failed due to internal error.

container: input

uses: vtn-flow-filter-id

refines:

leaf: output

description: Describes the flow direction for the flow filter. If true, the flow filter list for outgoing packets is targeted. If false or omitted, the flow filter list for incoming packets is targeted.
type: (urn:ietf:params:xml:ns:yang:1)boolean

leaf: tenant-name

description: The name of the VTN.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: bridge-name

description: The name of the vBridge. This field is omitted if the virtual node specified by this model is neither a vBridge nor a virtual node attached to the vBridge.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: router-name

description: The name of the vRouter. Currently the VTN Manager never uses this field because the virtual router is not yet supported.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: terminal-name

description: The name of the vTerminal. This field is ignored if `bridge-name' field is configured. This field is omitted if the virtual node specified by this model is neither a vTerminal nor a virtual node attached to the vTerminal.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf: interface-name

description: The name of the virtual interface. - If the virtual interface specified by this model is attached to a vBridge, the name of the vBridge is set to `bridge-name' field. - If the virtual interface specified by this model is attached to a vTerminal, the name of the vTerminal is set to `terminal-name' field. - This field is omitted if the virtual node specified by this model is not a virtual interface.
type: (urn:ietf:params:xml:ns:yang:1)string

leaf-list: indices

description: A list of flow filter index numbers to be removed from the flow filter list specified by the RPC input. If this field is omitted or an empty list is specified, all the flow filters present in the specified flow filter list will be removed. Duplicates in this list will be eliminated automatically.
type: int32

container: output

uses: vtn-flow-filter-result

refines:

list: flow-filter-result

description: Describes a pair of flow filter index and `vtn-update-type' value.

uses: (urn:opendaylight:vtn:types)vtn-rpc-result

refines:

leaf: index

description: One of flow filter indicies specified by the RPC input.
type: (urn:ietf:params:xml:ns:yang:1)int32

leaf: status

description: Describes the status of the RPC result.
type: (urn:opendaylight:vtn:types)vtn-update-type

vtn-flow-filter

Base Information

Groupings Summary

RPCs Summary

Groupings

vtn-redirect-filter-config

vtn-flow-filter-result

vtn-flow-filter-list

vtn-flow-filter-config

vtn-flow-filter-id

vtn-flow-filter-type-fields

RPC Definitions

set-flow-filter

remove-flow-filter