The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The examples of SVO data models are as follows:
Example 1: The following example shows the RPC Request and RPC Response messages to get information about a particular node.
RPC Request
<?xml version="1.0" encoding="utf-8"?>
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="7">
<get>
<filter>
<svo xmlns="http://cisco.com/yang/svo">
<node-information></node-information>
</svo>
</filter>
</get>
</rpc>
RPC Response
<?xml version="1.0" encoding="utf-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="7">
<data>
<svo xmlns="http://cisco.com/yang/svo">
<node-information>
<name>SANITY_DEVICE_263</name>
<optical-type xmlns:ccet="http://cisco.com/yang/svo/common-equipment-types">ccet:roadm</optical-type>
<network-config>
<ip-address>10.58.226.118</ip-address>
</network-config>
<tdm-terminology-type xmlns:ccet="http://cisco.com/yang/svo/common-equipment-types">ccet:ansi</tdm-terminology-type>
<sw-version>12.1.0.B0263</sw-version>
<admin-plane-sw-version>12.1.0.B0263</admin-plane-sw-version>
<ha-manager-sw-version>12.1.0.B0263</ha-manager-sw-version>
<time-settings>
<enable-date-and-time>false</enable-date-and-time>
<ntp-svo>
<server-address>10.58.228.2</server-address>
<backup-server-address>10.58.228.3</backup-server-address>
</ntp-svo>
<ntp-devices>
<primary-server>0.0.0.0</primary-server>
<secondary-server>0.0.0.0</secondary-server>
</ntp-devices>
<ntp-card-controllers>
<server-address>0.0.0.0</server-address>
<backup-server-address>0.0.0.0</backup-server-address>
</ntp-card-controllers>
<time-zone>UTC</time-zone>
</time-settings>
</node-information>
</svo>
</data>
</rpc-reply>
Example 2: The following example shows the RPC Request and RPC Response messages to lock the running datastore.
RPC Request
<?xml version="1.0" encoding="utf-8"?>
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="567">
<lock>
<target>
<running></running>
</target>
</lock>
</rpc>
RPC Response
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="567"><ok/></rpc-reply>