When testing a device config it is useful to be able to actually place a request on the device in order to test the structure of the request.  That request can be utilized as a basis for creating a template in CDT Tool.  Testing directly on the device outline below is not necessary for testing with CDT/APPC.

Reference sites:


Note:  "]]>]]>" in the below example is the command to end/enter your input.

Example of Adding a vDNS Instance to the vLoadBalancer
]]>]]><rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
        <edit-config>
                <default-operation>merge</default-operation>
                <target>
                        <candidate/>
                </target>
                <config>
                                <vlb-business-vnf-onap-plugin xmlns="urn:opendaylight:params:xml:ns:yang:vlb-business-vnf-onap-plugin">
                                        <vdns-instances>
                                                <vdns-instance>
                                                        <ip-addr>192.168.10.212</ip-addr>
                                                        <oam-ip-addr>10.0.150.4</oam-ip-addr>
                                                        <enabled>true</enabled>
                                                </vdns-instance>
                                        </vdns-instances>
                                </vlb-business-vnf-onap-plugin>
                </config>
        </edit-config>
</rpc>
]]>]]>
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<ok/>
</rpc-reply>
]]>]]><rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<commit/>
</rpc>
]]>]]>
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<ok/>
</rpc-reply>
]]>]]>
  • No labels