hc2vpp@lists.fd.io | interfaces-state not in schema

Home Messages Hashtags Subgroups

Date Date 1 - 4 of 4

interfaces-state not in schema

Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...> #256 Moving to hc2vpp list. Regards, Marek toggle quoted message Show quoted text From: vpp-dev-bounces@... [mailto:vpp-dev-bounces@...] On Behalf Of sivan.b@... Sent: 5 stycznia 2018 22:26 To: vpp-dev@... Subject: [vpp-dev] interfaces-state not in schema I have been trying to configure VPP interfaces through Honeycomb. When I request all operational data using – <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101"> <get/> </rpc> I have a section in the output involving the interfaces – <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <phys-address>02:fe:9d:d8:52:86</phys-address> <admin-status>up</admin-status> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <address> <ip>192.168.93.171</ip> <prefix-length>24</prefix-length> </address> … And so, in order to configure the interfaces, I send a request like this: <rpc message-id="m-7" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <candidate/> </target> <config> <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <oper-status>up</oper-status> <admin-status>up</admin-status> </interface> </interfaces-state> </config> </edit-config> </rpc> However I receive the following error: <ERROR>org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaValidationFailedException: Child /(urn:ietf:params:xml:ns:yang:ietf-interfaces?revision=2014-05-08)interfaces-state is not present in schema tree.</ERROR> What is the reason for this? Am I forming the configuration request wrong? Thanks, Sivan.
More All Messages By This Member
Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...> #257 Hi, please use interfaces node instead of interfaces-state in your edit-config rpc. The interfaces-state node is defined as “config false” (see [1], [2]). Regards, Marek [1] http://www.netconfcentral.org/modules/ietf-interfaces [2] https://tools.ietf.org/html/rfc6020#section-4.2.3 - vpp-dev toggle quoted message Show quoted text From: vpp-dev-bounces@... [mailto:vpp-dev-bounces@...] On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) Sent: 8 stycznia 2018 07:41 To: sivan.b@...; vpp-dev@...; hc2vpp@... Subject: Re: [vpp-dev] interfaces-state not in schema Moving to hc2vpp list. Regards, Marek From: vpp-dev-bounces@... [mailto:vpp-dev-bounces@...] On Behalf Of sivan.b@... Sent: 5 stycznia 2018 22:26 To: vpp-dev@... Subject: [vpp-dev] interfaces-state not in schema I have been trying to configure VPP interfaces through Honeycomb. When I request all operational data using – <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101"> <get/> </rpc> I have a section in the output involving the interfaces – <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <phys-address>02:fe:9d:d8:52:86</phys-address> <admin-status>up</admin-status> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <address> <ip>192.168.93.171</ip> <prefix-length>24</prefix-length> </address> … And so, in order to configure the interfaces, I send a request like this: <rpc message-id="m-7" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <candidate/> </target> <config> <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <oper-status>up</oper-status> <admin-status>up</admin-status> </interface> </interfaces-state> </config> </edit-config> </rpc> However I receive the following error: <ERROR>org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaValidationFailedException: Child /(urn:ietf:params:xml:ns:yang:ietf-interfaces?revision=2014-05-08)interfaces-state is not present in schema tree.</ERROR> What is the reason for this? Am I forming the configuration request wrong? Thanks, Sivan.
More All Messages By This Member
sivan.b@campus.technion.ac.il <sivan.b@...> #258 Thanks for the reply, As you suggested, using interfaces instead of interfaces-state for configuration works, however it seems I cannot use it to read data from the device. The following request fails: <rpc message-id="m-0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree"> <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"/> </filter> </get> </rpc> ]]>]]> With this error: <ERROR>java.lang.NullPointerException: Unable to read InstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.interfaces.rev140508.Interfaces, path=[org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.interfaces.rev140508.Interfaces]}. Missing reader. Current readers for: [interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.interfaces.rev140508.InterfacesState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.v3po.rev170607.BridgeDomainsState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.v3po.context.rev160909.DisabledInterfaces, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.dhcp.rev170315.Dhcp, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.nat.rev150908.NatState, interface org.opendaylight.yang.gen.v1.urn.honeycomb.params.xml.ns.yang.naming.context.rev160513.Contexts, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.policer.rev170315.PolicersState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.gpe.rev170801.GpeState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.gpe.rev170801.NativeForwardPathsTablesState, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.access.control.list.rev160708.AccessLists, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.classifier.rev170327.VppClassifierState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.classifier.context.rev170502.VppClassifierContext, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.netconf.monitoring.rev101004.NetconfState, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.netmod.notification.rev080714.Netconf, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.management.rev170315.VppState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.lisp.rev171013.LispState, interface org.opendaylight.yang.gen.v1.urn.honeycomb.params.xml.ns.yang.eid.mapping.context.rev160801.Contexts, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.routing.rev140524.RoutingState]</ERROR> Is there any one single node I can use both for configuring and reading from VPP? Thanks again, Sivan. toggle quoted message Show quoted text From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) [mailto:mgradzki@...] Sent: Monday, January 8, 2018 8:43 AM To: Sivan Ben-Haim <sivan.b@...>; hc2vpp@... Cc: honeycomb-dev@... Subject: RE: interfaces-state not in schema Hi, please use interfaces node instead of interfaces-state in your edit-config rpc. The interfaces-state node is defined as “config false” (see [1], [2]). Regards, Marek [1] http://www.netconfcentral.org/modules/ietf-interfaces [2] https://tools.ietf.org/html/rfc6020#section-4.2.3 - vpp-dev From: vpp-dev-bounces@... [mailto:vpp-dev-bounces@...] On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) Sent: 8 stycznia 2018 07:41 To: sivan.b@...; vpp-dev@...; hc2vpp@... Subject: Re: [vpp-dev] interfaces-state not in schema Moving to hc2vpp list. Regards, Marek From: vpp-dev-bounces@... [mailto:vpp-dev-bounces@...] On Behalf Of sivan.b@... Sent: 5 stycznia 2018 22:26 To: vpp-dev@... Subject: [vpp-dev] interfaces-state not in schema I have been trying to configure VPP interfaces through Honeycomb. When I request all operational data using – <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101"> <get/> </rpc> I have a section in the output involving the interfaces – <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <phys-address>02:fe:9d:d8:52:86</phys-address> <admin-status>up</admin-status> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <address> <ip>192.168.93.171</ip> <prefix-length>24</prefix-length> </address> … And so, in order to configure the interfaces, I send a request like this: <rpc message-id="m-7" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <candidate/> </target> <config> <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <oper-status>up</oper-status> <admin-status>up</admin-status> </interface> </interfaces-state> </config> </edit-config> </rpc> However I receive the following error: <ERROR>org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaValidationFailedException: Child /(urn:ietf:params:xml:ns:yang:ietf-interfaces?revision=2014-05-08)interfaces-state is not present in schema tree.</ERROR> What is the reason for this? Am I forming the configuration request wrong? Thanks, Sivan.
More
Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES@Cisco) <mgradzki@...> #259 Hi, <get> for <interfaces> is currently not supported, but it works for <interfaces-state>. It should not be hard to add. I can give you some pointers if you want. For asymmetric models like ietf-interfaces (with xxx and xxx-state), we unusually do not provide <get> for xxx nor <get-config> for <xxx-state> (nat is another example: https://jira.fd.io/browse/HC2VPP-240). Only <get> for xxx-state and <get-config> for xxx. Symmetric models do not have such limitations (e.g. dhcp, ietf-access-control-list). Regards, Marek toggle quoted message Show quoted text From: sivan.b@... [mailto:sivan.b@...] Sent: 9 stycznia 2018 20:24 To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; hc2vpp@... Cc: honeycomb-dev@... Subject: RE: interfaces-state not in schema Thanks for the reply, As you suggested, using interfaces instead of interfaces-state for configuration works, however it seems I cannot use it to read data from the device. The following request fails: <rpc message-id="m-0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <get> <filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree"> <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"/> </filter> </get> </rpc> ]]>]]> With this error: <ERROR>java.lang.NullPointerException: Unable to read InstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.interfaces.rev140508.Interfaces, path=[org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.interfaces.rev140508.Interfaces]}. Missing reader. Current readers for: [interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.interfaces.rev140508.InterfacesState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.v3po.rev170607.BridgeDomainsState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.v3po.context.rev160909.DisabledInterfaces, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.dhcp.rev170315.Dhcp, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.nat.rev150908.NatState, interface org.opendaylight.yang.gen.v1.urn.honeycomb.params.xml.ns.yang.naming.context.rev160513.Contexts, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.policer.rev170315.PolicersState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.gpe.rev170801.GpeState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.gpe.rev170801.NativeForwardPathsTablesState, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.access.control.list.rev160708.AccessLists, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.classifier.rev170327.VppClassifierState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.classifier.context.rev170502.VppClassifierContext, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.netconf.monitoring.rev101004.NetconfState, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.netmod.notification.rev080714.Netconf, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.vpp.management.rev170315.VppState, interface org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.lisp.rev171013.LispState, interface org.opendaylight.yang.gen.v1.urn.honeycomb.params.xml.ns.yang.eid.mapping.context.rev160801.Contexts, interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.ietf.routing.rev140524.RoutingState]</ERROR> Is there any one single node I can use both for configuring and reading from VPP? Thanks again, Sivan. From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) [mailto:mgradzki@...] Sent: Monday, January 8, 2018 8:43 AM To: Sivan Ben-Haim <sivan.b@...>; hc2vpp@... Cc: honeycomb-dev@... Subject: RE: interfaces-state not in schema Hi, please use interfaces node instead of interfaces-state in your edit-config rpc. The interfaces-state node is defined as “config false” (see [1], [2]). Regards, Marek [1] http://www.netconfcentral.org/modules/ietf-interfaces [2] https://tools.ietf.org/html/rfc6020#section-4.2.3 - vpp-dev From: vpp-dev-bounces@... [mailto:vpp-dev-bounces@...] On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) Sent: 8 stycznia 2018 07:41 To: sivan.b@...; vpp-dev@...; hc2vpp@... Subject: Re: [vpp-dev] interfaces-state not in schema Moving to hc2vpp list. Regards, Marek From: vpp-dev-bounces@... [mailto:vpp-dev-bounces@...] On Behalf Of sivan.b@... Sent: 5 stycznia 2018 22:26 To: vpp-dev@... Subject: [vpp-dev] interfaces-state not in schema I have been trying to configure VPP interfaces through Honeycomb. When I request all operational data using – <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101"> <get/> </rpc> I have a section in the output involving the interfaces – <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <phys-address>02:fe:9d:d8:52:86</phys-address> <admin-status>up</admin-status> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <address> <ip>192.168.93.171</ip> <prefix-length>24</prefix-length> </address> … And so, in order to configure the interfaces, I send a request like this: <rpc message-id="m-7" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <candidate/> </target> <config> <interfaces-state xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> <interface> <name>host-ens33</name> <oper-status>up</oper-status> <admin-status>up</admin-status> </interface> </interfaces-state> </config> </edit-config> </rpc> However I receive the following error: <ERROR>org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaValidationFailedException: Child /(urn:ietf:params:xml:ns:yang:ietf-interfaces?revision=2014-05-08)interfaces-state is not present in schema tree.</ERROR> What is the reason for this? Am I forming the configuration request wrong? Thanks, Sivan.
More All Messages By This Member

1 - 4 of 4

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms