H3C Technologies H3C S6300 Series Switches - Manual (Page 239)

226
NETCONF message format
NETCONF
IMPORTANT:
When configuring NETCONF in XML view, you must add "]]>]]>" at the end of an XML message.
Otherwise, the device fails to identify the message.
All NETCONF messages are XML-based and comply with RFC 4741. Any incoming NETCONF messages
must pass XML Schema check before it can be processed. If a NETCONF message fails XML Schema
check, the device sends an error message to the client.
For information about the NETCONF operations supported by the device and the operable data, see the
NETCONF XML API reference for the switch.
The following example shows a NETCONF message for getting all parameters of all interfaces on the
device:
<?xml version="1.0" encoding="utf-8"?>
<rpc message-id ="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-bulk>
<filter type="subtree">
<top xmlns="http://www.h3c.com/netconf/data:1.0">
<Ifmgr>
<Interfaces>
<Interface/>
</Interfaces>
</Ifmgr>
</top>
</filter>
</get-bulk>
</rpc>
How to use NETCONF
You can use NETCONF to manage and configure the device by using the methods in Table 28 .
Table 28 NETCONF methods for configuring the device
Configuration tool Login method Remarks
CLI
• Console port
• SSH
• Telnet
To implement NETCONF operations, copy valid
NETCONF messages to the CLI in XML view.
This method is suitable for R&D and test
purposes.
Custom Web interface N/A
To use this method, you must enable NETCONF
over SOAP.
By default, the device cannot interpret custom
Web interfaces' URLs. For the device to interpret
these URLs, you must encode the NETCONF
messages sent from a custom Web interface in
SOAP.