# netconf\_config - Viptela

**URL:** <https://forum.ansible.com/t/netconf-config-viptela/29734>\
**Category:** Ansible Project\
**Created:** [February 21, 2019, 2:14pm UTC](https://forum.ansible.com/t/netconf-config-viptela/29734 "2019-02-21T14:14:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![robbiee.dwyer](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@robbiee.dwyer](https://forum.ansible.com/u/robbiee.dwyer)\
**Post date:** [February 21, 2019, 2:14pm UTC](https://forum.ansible.com/t/netconf-config-viptela/29734/1 "2019-02-21T14:14:30Z")

</div>

Hello,

I am trying to use netconf\_config module on vEdge 18.3 without success.

---

<div class="post-metadata">

**Author:** ![ganeshrn](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ganeshrn/32/1021_2.png) [@ganeshrn](https://forum.ansible.com/u/ganeshrn)\
**Post date:** [February 21, 2019, 3:33pm UTC](https://forum.ansible.com/t/netconf-config-viptela/29734/2 "2019-02-21T15:33:30Z")

</div>

> “Element [{[http://tail-f.com/ns/config/1.0}config](http://tail-f.com/ns/config/1.0%7Dconfig)] does not meet requirement”

Based on the error received from netconf server running on target host it seems the rooted xml payload is not supported  
by the server. As per netconf rfc for edit-config RPC the config value should have “config” element mandatory as root.

What the value of “content” option when using netconf\_rpc module?

---

<div class="post-metadata">

**Author:** ![robbiee.dwyer](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@robbiee.dwyer](https://forum.ansible.com/u/robbiee.dwyer)\
**Post date:** [February 21, 2019, 3:49pm UTC](https://forum.ansible.com/t/netconf-config-viptela/29734/3 "2019-02-21T15:49:37Z")

</div>

The only difference with the RPC call is that I have to put in.

ok: [sdw-ssc-vbond-g01] =\> {  
“changed”: false,  
“invocation”: {  
“module\_args”: {  
“content”: “\n \n\n\<config xmlns="[http://tail-f.com/ns/config/1.0\](http://tail-f.com/ns/config/1.0%5C)”\>\n \<system xmlns="[http://viptela.com/system\](http://viptela.com/system%5C)“\>\n scooberdoober\n \n\n”,  
“display”: null,  
“rpc”: “edit-config”,  
“xmlns”: null  
}  
},  
“output”: null,  
“stdout”: “\<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:1e74d2f9-be5e-4be1-8543-a990b7d207e4"\>”,  
“stdout\_lines”: [  
“\<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:1e74d2f9-be5e-4be1-8543-a990b7d207e4"\>”  
]  
}

---

<div class="post-metadata">

**Author:** ![ganeshrn](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ganeshrn/32/1021_2.png) [@ganeshrn](https://forum.ansible.com/u/ganeshrn)\
**Post date:** [February 21, 2019, 4:07pm UTC](https://forum.ansible.com/t/netconf-config-viptela/29734/4 "2019-02-21T16:07:32Z")

</div>

The error is reported from ncclient. For edit-config RPC it tries to validate if the is the root element of XML payload [1] & [2].  
Since namespace is added to the config element it results in failure. Please remove namespace from “config” element and try again.

[1] [https://github.com/ncclient/ncclient/blob/master/ncclient/operations/edit.py#L62](https://github.com/ncclient/ncclient/blob/master/ncclient/operations/edit.py#L62)

[2] [https://github.com/ncclient/ncclient/blob/master/ncclient/xml\_.py#L147](https://github.com/ncclient/ncclient/blob/master/ncclient/xml_.py#L147)

---

<div class="post-metadata">

**Author:** ![robbiee.dwyer](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@robbiee.dwyer](https://forum.ansible.com/u/robbiee.dwyer)\
**Post date:** [February 21, 2019, 4:14pm UTC](https://forum.ansible.com/t/netconf-config-viptela/29734/5 "2019-02-21T16:14:41Z")

</div>

Thanks Ganesh, thought I had tried that but apparently not :-). Working now.

-Rob