NETCONF in SR OS
Page 338 7450 ESS System Mangement Guide
<get>
CLI content layer <get> operation is supported. XML content layer <get> operation is not
supported.
A <get> request is first analyzed for syntax errors before any execution starts. If a syntax error
is found then a single global <rpc-error> for the entire request is sent in the reply.
Responses are provided for each item in the request until the first item with an error is found.
The item with an error has a <response> tag containing some error information, followed by
an <rpc-error> tag (and sub-tags). The reply is then returned and subsequent items are not
executed.
The <rpc-error> for an individual item (i.e. for a non-syntax error) is after the </response>
information and not inside the <response>.
Example — <get> request with a non-syntax error in the 2nd item:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter>
<oper-data-format-cli-block>
<cli-show>router interface "system"</cli-show>
<cli-show>router mpls lsp</cli-show>
<cli-show>system security ssh</cli-show>
</oper-data-format-cli-block>
</filter>
</get>
</rpc>
]]>]]>
Reply:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data xmlns="urn:alcatel-lucent.com:sros:ns:yang:cli-content-layer-r13">
<oper-data-format-cli-block>
<item>
<cli-show>router interface "system"</cli-show>
<response>
===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
system Up Up/Down Network system
144.23.63.5/32 n/a
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
</response>