y the error severity. - <statement> This tag gives the cause of the error. - <message> This is a string description of the error condition. Additional attributes like <action> can be used to describe the action to be taken when the specific error is encountered and <edit-path> to describe the error. <rpc-error message-id = 215> <tag>SAMPLE_CRC_LOG</tag> <error-code>512</error-code> kseverity>error</severity> <statement>CRO 250; </statement> <message>CRC 250 on Interface Card</message> </rpc-error> 32.4 NETCONF Operations Some of the basic protocol operations in NETCONF are discussed in this section. I. <get-config> This operation retrieves the configuration data. Application Layer <!-- Example Request <rpc message-id="212" xmlns="http://ietf.org/ xmlconf/1.0/base"> <get-config> <source><running/></source> <config xmlns="http://example.com/ schema/1.2/config"> <users> <user> <name>jithesh</name> </user> </users> </config> <format>xml</format> </get-config> </rpc> <!-- Example Response <rpc-reply - message-id="212" xmlns="http://ietf.org/ xmlconf/1./base"> <config xmlns="http://example.com/schema/1.2/ config"> <users> <user> <name>jithesh</name> <type>admin</type> <full-name>Jithesh Sathyan</ full-name> </user> </users> </config> </rpc-reply> II. <edit-config> This operation is used to load all or part of a specified con- figuration to a defined target configuration. The new configuration can be expressed inline or using local/remote file. <!- Example Request <rpc message-id="216" xmlns="http://ietf.org/ xmlconf/1.0/base"> <edit-config> <target> <running/></target> <config xmlns="http://example.com/ schema/1.2/config"> Fundamentals of EMS, NMS and OSS/BSS <interface> k<name>ExternalRouter 6</ name> <router>15</router> </interface> </config> </edit-config> </rpc> <!-- Example Response <rpc-reply - message-id="216" xmlns="http://ietf.org/ xmlconf/1./base"> <ok/> </rpc-reply> III. <copy-config> This operation is used to copy a configuration file onto another configuration file. In this process the file to which conten