Skip to content
AsterNOS

Feature‑Control

This chapter provides an example of how to use Netconf to manage feature control configuration on AsterNOS devices.

hint{type=“warning”} NOTE: The running-status is a read-only leaf and can only be retrieved via get operation.

Request example to get Feature Running Status via get with subtree filter.

<filter type="subtree">
  <top>
    <features-control>
      <feature>
        <name>dhcp_relay</name>
        <running-status/>
      </feature>
    </features-control>
  </top>
</filter>

Response example

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:311e281a-e7f5-4cff-ab5a-3ee1f9bcf69d">
  <data>
    <top>
      <features-control xmlns="http://asterfusion.com/ns/yang/asternos-feature-control">
        <feature>
          <name>dhcp_relay</name>
          <running-status>enabled</running-status>
        </feature>
      </features-control>
    </top>
  </data>
</rpc-reply>

Modify Feature Control Entry

Section titled “Modify Feature Control Entry”

Request example to modify specific Feature Control Entry via edit-config with merge operation.

<config>
  <top>
    <features-control>
      <feature>
        <name>dhcp_relay</name>
        <admin-state>enable</admin-state>
      </feature>
    </features-control>
  </top>
</config>

Response example

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:88dea55e-1d67-4468-a4ed-7b8369f28734">
  <ok/>
</rpc-reply>