Exchanging Initialization Pis And Tag Elements; Sending An Operational Request; Locking The Configuration - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Exchanging Initialization PIs and Tag Elements

Sending an Operational Request

Locking the Configuration

Copyright © 2010, Juniper Networks, Inc.
Locking the Configuration on page 57
Changing the Configuration on page 58
Committing the Configuration on page 58
Unlocking the Configuration on page 59
Closing the Junos XML Protocol Session on page 59
After the client application establishes a connection to a Junos XML protocol server, the
two exchange initialization PIs and tag elements, as shown in the following example.
Note that the Junos XML protocol server's opening
lines for legibility only. Neither the Junos XML protocol server nor client applications insert
a newline character into the list of attributes. Also, in an actual exchange, the
variable is replaced by a value such as
JUNOS-release
OS Release 10.3. For a detailed discussion of the
tag, see "Starting the Junos XML Protocol Session" on page 38.
Client Application
<?xml version="1.0" encoding="us-ascii"?>
<junoscript version="1.0" release=" JUNOS-release ">
The client application now emits the
information about the device's chassis hardware. The Junos XML protocol server returns
the requested information in the
Client Application Junos XML Protocol Server
<rpc>
<get-chassis-inventory>
<detail/>
</get-chassis-inventory>
</rpc>
<rpc-reply xmlns:junos="URL ">
</rpc-reply>
The client application then prepares to create a new privilege class called
at the
[edit system login class]
Chapter 3: Controlling the Junos XML Management Protocol Session
<junoscript>
10.3R1
<?xml?>
Junos XML Protocol Server
<?xml version="1.0" encoding="us-ascii"?>
<junoscript version="1.0" hostname="router1" \
os="JUNOS" release="JUNOS-release " \
xmlns="URL "xmlns:junos=" URL " \
xmlns:xnm="URL ">
<get-chassis-inventory>
tag element.
<chassis-inventory>
<chassis-inventory xmlns="URL ">
<chassis>
<name>Chassis</name>
<serial-number>1122</serial-number>
<description>M320</description>
<chassis-module>
<name>Midplane</name>
<!- - other child tags for the Midplane- ->
</chassis-module>
<!- - tags for other chassis modules- ->
</chassis>
</chassis-inventory>
hierarchy level. It begins by using the
tag appears on multiple
for the initial version of Junos
PI and opening <junoscript>
tag element to request
network-mgmt
<lock-configuration/>
57