[Contents] [Prev] [Next] [Index] [Report an Error]

Operational Responses

Operational responses are responses to requests for information about routing platform status. They correspond to the output from CLI operational commands as described in the JUNOS command references.

The JUNOS XML API defines response tag elements for all defined operational request tag elements. For example, the NETCONF server returns the information requested by the <get-interface-information> tag element in a response tag element called <interface-information>, and the information requested by the <get-chassis-inventory> tag element in a response tag element called <chassis-inventory>.

The following sample response includes information about the interface called ge-2/3/0. The namespace indicated by the xmlns attribute in the opening <interface-information> tag is for interface information in the initial version of JUNOS Release 9.4. The opening tags appear on two lines here for legibility only:



<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"\
                xmlns:junos="http://xml.juniper.net/junos/9.4R1/junos">
    <interface-information \
                xmlns="http://xml.juniper.net/junos/9.4R1/junos-interface">
        <physical-interface>
            <name>ge-2/3/0</name>
            <!- - other data tag elements for the ge-2/3/0 interface -  ->
        </physical-interface>
    </interface-information>
</rpc-reply>
]]>]]>

For more information about the xmlns attribute and the contents of operational response tag elements, see Requesting Operational Information. For a summary of operational response tag elements, see the JUNOS XML API Operational Reference.

[Contents] [Prev] [Next] [Index] [Report an Error]