04-24-2019 01:33 AM - edited 04-24-2019 01:50 AM
Netconf NED is generating the below query ware key tag is used twice.
In the below request number tag is added twice.
<number>3</number>
<number/>
is this as per netconf standard, how to avoid this double tag?
>>>>out 24-Apr-2019::11:05:19.244 user: admin/82 thandle 1 device bo1 session-id=3671848952
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="1811">
<get>
<filter>
<optics-oper xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-controller-optics-oper">
<optics-ports>
<optics-port>
<name>Optics0/0/0/9</name>
<optics-lanes>
<optics-lane>
<number>3</number>
<frequency-offset/>
<number/>
<lane-index/>
<laser-bias-current-percent/>
<laser-bias-current-milli-amps/>
<transmit-power/>
<receive-power/>
<receive-signal-power/>
<transmit-signal-power/>
<output-frequency/>
</optics-lane>
</optics-lanes>
</optics-port>
</optics-ports>
</optics-oper>
</filter>
</get>
</rpc>
<<<<in 24-Apr-2019::11:05:19.250 user: admin/82 thandle 1 device bo1 session-id=3671848952
<rpc-reply message-id="1811"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-message xml:lang="en">'YANG framework' detected the 'fatal' condition 'Invalid argument specified'</error-message>
</rpc-error>
</rpc-reply>
-Pradeep
Solved! Go to Solution.
04-25-2019 07:09 AM
@pradc wrote:
Netconf NED is generating the below query ware key tag is used twice.
In the below request number tag is added twice.
<number>3</number>
<number/>is this as per netconf standard, how to avoid this double tag?
Yes, this is indeed valid according to the Netconf standard.
See https://tools.ietf.org/html/rfc6241#section-6.2, specifically "Selection Nodes" and "Content Match Nodes".
In this case, <number>3</number> is a Content Match node. It is for the exact match of the key.
<number/> tag is a Selection node. It is not an error to use a node as a selection node, even if the same node has already been used as a content-match node.
I'm not sure how to avoid this, though. I can't think of a mechanism to control the way that NSO builds the RPCs towards devices.
/Ram
04-25-2019 07:09 AM
@pradc wrote:
Netconf NED is generating the below query ware key tag is used twice.
In the below request number tag is added twice.
<number>3</number>
<number/>is this as per netconf standard, how to avoid this double tag?
Yes, this is indeed valid according to the Netconf standard.
See https://tools.ietf.org/html/rfc6241#section-6.2, specifically "Selection Nodes" and "Content Match Nodes".
In this case, <number>3</number> is a Content Match node. It is for the exact match of the key.
<number/> tag is a Selection node. It is not an error to use a node as a selection node, even if the same node has already been used as a content-match node.
I'm not sure how to avoid this, though. I can't think of a mechanism to control the way that NSO builds the RPCs towards devices.
/Ram
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide