Hi, Marek Gradzki:
I want to filter v3po’s bridge-domains-state container as two level,first level is bridge-domain’s key (name),the second level is l2-fib-entry’s key (phys-address),but the second level does not work(The other two l2-fib-entry also appeared),please see the following log:
The xml is :
<rpc message-id="m-1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter>
<bridge-domains-state xmlns="urn:opendaylight:params:xml:ns:yang:v3po">
<bridge-domain>
<name>bridge-domain-200</name>
<l2-fib-table>
<l2-fib-entry>
<phys-address>76:c5:17:f7:ff:03</phys-address>
</l2-fib-entry>
</l2-fib-table>
</bridge-domain>
</bridge-domains-state>
</filter>
</get>
</rpc>
]]>]]>
The result is:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-1">
<data>
<bridge-domains-state xmlns="urn:opendaylight:params:xml:ns:yang:v3po">
<bridge-domain>
<name>bridge-domain-200</name>
<learn>true</learn>
<unknown-unicast-flood>true</unknown-unicast-flood>
<flood>true</flood>
<arp-termination>true</arp-termination>
<forward>true</forward>
<l2-fib-table>
<l2-fib-entry>
<phys-address>76:c5:17:f7:ff:03</phys-address>
<action>l2-fib-forward</action>
<outgoing-interface>tapcli-1</outgoing-interface>
<static-config>false</static-config>
<bridged-virtual-interface>false</bridged-virtual-interface>
</l2-fib-entry>
<l2-fib-entry>
<phys-address>6e:34:26:28:88:74</phys-address>
<action>l2-fib-forward</action>
<outgoing-interface>tapcli-0</outgoing-interface>
<static-config>false</static-config>
<bridged-virtual-interface>false</bridged-virtual-interface>
</l2-fib-entry>
<l2-fib-entry>
<phys-address>de:ad:00:00:00:02</phys-address>
<action>l2-fib-forward</action>
<outgoing-interface>loop2</outgoing-interface>
<static-config>true</static-config>
<bridged-virtual-interface>true</bridged-virtual-interface>
</l2-fib-entry>
</l2-fib-table>
</bridge-domain>
</bridge-domains-state>
</data>
</rpc-reply>
]]>]]>
