Send <copy-config>, <validate-config>, and <kill-ssession> (NETCONF)
=========================================================================

Kill session
-------------
    You need to kill a session that may be unexpectely holding the datastore lock.

    To invoke NETCONF kill-session RPC, click the ``kill-session`` toolbar button.
    
    .. image:: images/kill_session.*    
    
    You need to enter the session ID you want to kill.
    One way to find the sesion ID is by looking at netconf-monitoring module as shown below:
    
    .. image:: images/find_session_id.*    
    
Validate config
----------------------
    
   If ``Validate`` capability is advertised, the device supports the <validate>
   protocol operation and checks at least for syntax errors for the config data supplied.
   
    To invoke NETCONF <validate> opertion, click the ``validate config`` toolbar button.
    
    .. image:: images/validate_config.*    
    
copy-config,  backup and restore 
-----------------------------------
    To invoke NETCONF copy-config opertion, click the ``copy-config`` button.
    
    .. image:: images/copy_config.*    
    
    The running config can be saved into a file as a checkpoint before updating it.
    If updating fails, it can be restored by reloading the checkpoint file.

    The checkpoint file can be created by using a file url as the target. For Example:
    
    Save checkpoint config file into a file on the server's root directory:
    
    ``Target:  file:///checkpoint.conf``, (note it has three '/' here!)
    
    Save checkpoint config file into a file under a user home directory on the server:
    
    ``Target:  file:///home/joe/checkpoint.conf``, (note it has three '/' here!)
    
    Save checkpoint config file into a file on a network location:
     
    ``Target:  file://host-name/checkpoint.conf``, or if host name is omitted, 

    To restore the checkpoint file, reverse the <source> and <target>  parameters

    A with-defaults option can also be selected. However the <copy-config> operation 
    is only affected by the <with-defaults> parameter
    if the target of the operation is specified with the <url> parameter.
