Siemens RX1400 - Retrieving OSPF Status

Chapter 7
Examples
RUGGEDCOM NETCONF
Reference Guide
108 Retrieving OSPF Status
<routing xmlns="http://ruggedcom.com/ns/rmf_routing">
<dynamic>
<ospf>
<enabled/>
</ospf>
</dynamic>
</routing>
</config>
</edit-config>
</rpc>]]>]]>
5. Commit the changes:
<rpc message-id="234" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit/>
</rpc>]]>]]>
6. Unlock the candidate configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="235">
<unlock>
<target>
<candidate/>
</target>
</unlock>
</rpc>]]>]]>
7. Unlock the running configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="236">
<unlock>
<target>
<running/>
</target>
</unlock>
</rpc>]]>]]>
Section7.31
Retrieving OSPF Status
In this example, a single <rpc> request retrieves the OSPF status information from the running configuration on a
device.
The following is the typical procedure for querying data from the running configuration.
• Request the data from the running configuration:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<action xmlns="http://tail-f.com/ns/netconf/actions/1.0">
<data>
<routing xmlns="http://ruggedcom.com/ns/rmf_routing">
<status>
<ospf_status/>
</status>
</routing>
</data>
</action>
</rpc>]]>]]>