Navigation
Related Documentation
- Parsing the NETCONF Server Response
- <data>
- <ok/>
- <output> in the Junos XML API Operational Reference
- <rpc>
- <rpc-error>
<rpc-reply>
Usage
<rpc-reply xmlns="URN" xmlns:junos="URL"><!-- tag elements in a reply from the NETCONF server--></rpc-reply>
]]>]]>Description
Enclose all tag elements in a reply from the NETCONF server. The immediate child tag element is usually one of the following:
- The Junos XML tag element that encloses the data requested by a client application with a Junos XML operational request tag element; for example, the <interface-information> tag element in response to the <get-interface-information> tag element
- The <data> tag element, to enclose the data requested by a client application with the <get-config> tag element
- The <ok/> tag, to confirm that the NETCONF server successfully performed an operation that changes the state or contents of a configuration (such as a lock, change, or commit operation)
- The <output> tag element, if the Junos XML API does not define a specific tag element for requested operational information
- The <rpc-error> tag element, if the requested operation generated an error or warning
Attributes
xmlns | — | Names the default XML namespace for the enclosed tag elements. |
Related Documentation
- Parsing the NETCONF Server Response
- <data>
- <ok/>
- <output> in the Junos XML API Operational Reference
- <rpc>
- <rpc-error>
Published: 2013-07-26
Related Documentation
- Parsing the NETCONF Server Response
- <data>
- <ok/>
- <output> in the Junos XML API Operational Reference
- <rpc>
- <rpc-error>