A request tag element is one generated by a client application to request information about a routing platform’s current status or configuration, or to change the configuration. A request tag element corresponds to a CLI operational or configuration command. It can occur only within an <rpc> tag element. For information about the <rpc> tag element, see Sending a Request to the NETCONF Server.
A response tag element represents the NETCONF server’s reply to a request tag element and occurs only within an <rpc-reply> tag element. For information about the <rpc-reply> tag element, see Parsing the NETCONF Server Response.
The following example represents an exchange in which a client application emits the <get-interface-information> request tag element with the <extensive/> flag and the NETCONF server returns the <interface-information> response tag element.
 |
Note: This example, like all others in this guide, shows each tag element on a separate line, in the tag streams emitted by both the client application and NETCONF server. In practice, a client application does not need to include newline characters between tag elements, because the server automatically discards such white space. For further discussion, see Spaces, Newline Characters, and Other White Space. |
For information about the ]]>]]> character sequence, see Generating Well-Formed XML Documents. For information about the attributes in the opening <rpc-reply> tag, see Parsing the NETCONF Server Response. For information about the xmlns attribute in the opening <interface-information> tag, see Requesting Operational Information.
 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |