Using the custom action mechanism

An action is a proprietary mechanism used for implementing operations that do not affect the configuration datastore. Several implementations of actions exist in the Extreme SLX-OS implementation for retrieving operational information.

The following structure is defined in the extreme-zone.yang module for displaying operational data related to zoning.

<nc:rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="10">
	<nca:action xmlns:nca="http://tail-f.com/ns/netconf/actions/1.0">
		nca:data>
         <show xmlns="urn:brocade.com:mgmt:brocade-common-def">
            <license xmlns="urn:brocade.com:mgmt:brocade-license">
               <id></id>
            </license>
         </show>
      </nca:data>
	</nca:action>
</nc:rpc>

<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="10">
   <data>
      <show xmlns="urn:brocade.com:mgmt:brocade-common-def">
         <license xmlns="urn:brocade.com:mgmt:brocade-license">
            <id>
               <licenseid-list>
                  <license-id>10:00:F4:6E:95:9F:2E:F0</license-id>
               </licenseid-list>
            </id>
         </license>
      </show>
   </data>
</rpc-reply>

For a list of available actions and their locations, refer to the Extreme SLX-OS YANG Reference Manual.